Unable to download an Message Driven Bean Example

http://www.oracle.com/technology/sample_code/tech/java/oc4j/htdocs/oc4jsamplecode/oc4j-demo-ejb.html
In the link above try to download the example for Message Driven Bean. You can download it, but it is a "htm" file not a ear file that gets saved.
All other links open file (They all are jar files).
regards
-- Raghavan (Raag)

Hello Pascal,
The following article will assist you with resetting your BlackBerry ID password: http://www.blackberry.com/btsc/KB26361
Please try logging in with the new password when prompted.
Let us know if this helps.
-FB
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click "Accept as a Solution" for posts that have solved your issue(s)!

Similar Messages

Message driven bean example is not working

Hi,
i tried message driven bean example on J2ee 6.20. I am able to make connection factory, but when i tried to deploy ear file a get an exception:
Error occurred
com.inqmy.services.deploy.container.DeploymentException: java.lang.NullPointerEx
ception
        at com.inqmy.services.ejb20.EJBAdmin.commitDeploy(EJBAdmin.java:604)
        at com.inqmy.services.deploy.server.DeployServiceImpl.commit(DeployServi
ceImpl.java:2897)
        at com.inqmy.services.deploy.server.DeployServiceImpl.deploy1(DeployServ
iceImpl.java:524)
        at com.inqmy.services.deploy.server.DeployServiceImpl.deploy(DeployServi
ceImpl.java:139)
        at com.inqmy.services.deploy.command.DeployCommand.exec(DeployCommand.ja
va:142)
        at com.inqmy.services.shell.processor.environment.CommandBase.exec(Comma
ndBase.java:124)
        at com.inqmy.services.shell.processor.Interpreter.applyLineCommand(Inter
preter.java:391)
        at com.inqmy.services.shell.processor.Interpreter.apply(Interpreter.java
:150)
        at com.inqmy.services.shell.processor.Shell.work(Shell.java:150)
        at com.inqmy.services.shell.processor.managers.ScriptProcessThread.run(S
criptProcessThread.java:128)
in visual administrator I can see the right queue and for few seconds this queue have one consumer.
thank
JJ

Hi,
but this example was in guide to this version.
Ok, in case it is not possible to use MDB, how should i handle long time consumpting functions in EP enviroment?
(customer has only EP6SP2 and he need to send a lot of mails after user request and i dont want to leave user waiting till that function ends. - should i start new thread in portal?)
JJ

Problem creating Physical Destination for Message Driven Bean example

I am trying to create a MDB application. in which i want to distribute the workload using messages.
I am using SUN j2ee application server8.2 and netbeans 6.5 on windows xp professional.
I referred the j2ee 1.4 tutorial to create the mdb's.
I am able to create queue's and connection factories.
the tutorial says
To create the physical destination, perform the following steps:
.In the tree component, expand the Resources node, then expand the JMS Resources node.
.Select the Physical Destinations node.
.On the Physical Destinations page, click New. The Create Physical Destination page appears.
.In the Physical Destination Name field, type PhysicalQueue.
.Choose queue from the Type combo box.
.Click OK.
but i am not able to find out this Physical Destination node in admin console. So when i execute my MDB project the messages are created but the onMessage() method is not invoked.
Please help!!!

Hi,
but this example was in guide to this version.
Ok, in case it is not possible to use MDB, how should i handle long time consumpting functions in EP enviroment?
(customer has only EP6SP2 and he need to send a lot of mails after user request and i dont want to leave user waiting till that function ends. - should i start new thread in portal?)
JJ

Message Driven Bean example

Hi
I am looking for pointers in building a MDB Bean, pointers in this regard, will be of great help.
Thanks
sunder

http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
Good Luck,
Avi.

Assining Identity to Message Driven Bean

Dear All,
I have a problem on connecting MDB to JMS administered object in iPlanet server.
In the administered object I create an ACI to allows only a certain member of
group can access this ao. Disallowing anonymous user to connect to the ldap server
give me this error.
<Apr 15, 2003 1:41:09 PM SGT> <Warning> <EJB> <010096> <The Message-Driven EJB:
MessageEJB is unable to connect to the J
MS destination: cn=ocsQueue. Connection failed after 365 attempts. The MDB will
attempt to reconnect every 10 seconds, t
his log message will repeat every 600 seconds until the condition clears.>
<Apr 15, 2003 1:41:09 PM SGT> <Warning> <EJB> <010061> <The Message-Driven EJB:
MessageEJB is unable to connect to the J
MS destination: cn=ocsQueue. The EJB container will automatically attempt to re-establish
the connection with the JMS se
rver. This warning may occur during WebLogic Cluster start-up if the JMS destination
is located on another server. When
the JMS server connection is re-established, the Message-Driven EJB will again
receive JMS messages.
The Error was:
The Message-Driven EJB attempted to connect to the JMS destination with the JNDI
name: cn=ocsQueue. However, the object
with the JNDI name: cn=ocsQueue is not a JMS destination, or the destination found
was of the wrong type (Topic or Queue
).>
How can I configure the security descriptor so that my MDB can gen a connection
to ldap to read the administered object.
I am working on WebLogic 7.0 sp1 and iPlanet
Thanks,
Wayan

Hi Yang,
The J2EE tutorial will give some more information.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/
See Ch. 28 A Message-Driven Bean example. It has some tips on using deploytool.
Hope this helps,
J

Message-driven bean destination name not found error

Hi,
I am getting this error when I attempt to deploy the Warehouse message-driven bean example/tutorial. I followed the steps in the JMS Queue Simple Sample Application included with the server to set up the queue and queue factory, but I don't think the app. is even getting that far. I can not figure out why I'm get this error. I have looked at everything I can think of, but I'm obviously missing something. Here is the error from the server log.
INFO ( 2252): JMS5015: Install JMS resources ...
INFO ( 2252): JMS5002: Binding [< JMS Destination: jms/WarehouseQueue, javax.jms.Queue, [ imqDestinationName=WarehouseQueue ] >]
INFO ( 2252): JMS5002: Binding [< JMS Connection Factory: jms/WarehouseQueueConnectionFactory, javax.jms.QueueConnectionFactory, [ imqBrokerHostName=localhost , imqBrokerHostPort=7676 ] >]
INFO ( 2252): HTTP3072: HTTP listener http-listener-1 [http://ibankdev2:80] ready to accept requests
INFO ( 2252): CORE3274: successful server startup
INFO ( 2252): CORE5053: Application onReady complete.
INFO ( 2252): MDB00044: Deploying message-driven bean [MDBApp:Warehouse], consuming from [jms/Warehouse]
SEVERE ( 2252): MDB00015: [MDBApp:Warehouse]: Message-driven bean destination name [jms/Warehouse] not found
SEVERE ( 2252): javax.naming.NameNotFoundException
javax.naming.NameNotFoundException: Warehouse not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:185)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:157)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:161)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:78)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:375)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(LocalClientRequestImpl.java:96)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:237)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:279)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:138)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:317)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
SEVERE ( 2252): MDB00030: [MDBApp:Warehouse]: Exception in setting up message-driven bean container: [MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): MDB00017: [Warehouse]: Exception in creating message-driven bean container: [javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): javax.jms.JMSException
javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:340)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
SEVERE ( 2252): EJB5090: Exception in creating EJB container [javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): appId=MDBApp moduleName=EJBModule_Warehouse_jar ejbName=Warehouse
SEVERE ( 2252): LDR5004: UnExpected error occured while creating ejb container
javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:340)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
WARNING ( 2252): CORE5021: Application NOT loaded: [MDBApp]
WARNING ( 2252): ADM5603:Event listener error [Error while deploying application [MDBApp]. Please refer to the server log for more details. ]
My bean name is Warehouse, jms/Warehouse is the JNDI and is mapped to MDBPack.WarehouseBean.class. MDBPack is in the classpath on the server. I guessed that the physical destination name was WarehouseQueue, but using Warehouse produced the same result. Please let me know if there is anything I could be missing. TIA
--Michelle

Hi,
You have not created the jms destination queue object
jms/Warehouse
Your server logs says it cannot find the destination queue object.It has got nothing to do with jndi name of your bean
Create jms destination queue object using
asadmin>create-jms-resource instance <instance_name> resourcetype javax.jms.Queue --property imqDestinationName=<NAme> jms/Warehouse
Then use list-jms-resources <instance_name> to
find if jms/Warehouse destionation queue object has been created.
Get back in case of any issues

Message driven beans please help

Can anyone please provide me with a simple message driven bean example..
The examples i have found are not working..i dont know anything abt Message driven beans...i just need a sample working code because i need to deploy it on JBOSS using Ant.

Here's a simple EJB 3.0 JMS MDB from our glassfish ejb site :
https://glassfish.dev.java.net/javaee5/ejb/EJB30.html
--ken

Example for message-style with Message Driven Bean

hi,
Can i have some examples of webservices message-style with
MDB?....
thanks

The current version of the white-paper that Raffi
          refers to covers through 7.0. For 8.1 see also
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          and
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html
          these features can often make integration easier.
          Tom
          Raffi wrote:
          > Doug,
          >
          > You can find very detailed information on this topic at the link below. All
          > you need to do is specify the destination-jndi-name, initial-context-factory,
          > provider-url, and connection-factory-jndi-name in weblogic-ejb-jar.xml for the
          > non-BEA JMS provider for that specific MDB.
          >
          > ftp://edownload:[email protected]/pub/downloads/jmsproviders.pdf
          >
          > Hope that helps!
          >
          > Raffi
          >
          > Doug Chew <[email protected]> wrote:
          >
          >>Can someone give me an example on how to setup a message driven bean
          >>with a foreign JMS provider using the foreign JMS provider's implementation
          >>of a connection factory. i.e. binding the foreign JMS provider's connection
          >>factory to the JNDI tree.
          >>
          >>Thanks
          >
          >

Message Driven Bean debugging not supported in 9.0.3?

Message Driven Beans are now supported with the preview of 9.0.3, but you can't debug into them using the embedded container? Will this be resolved for the release version?

Brice --
Are you using the embedded help system or hosted documentation? I've just double-checked, and with the full jdev install, the "About Debugging PL/SQL Programs and Java Stored Procedures" is loading fine for me.
The PL/SQL variable should show up as well, without anything needing to be enabled on the server. What database version are you using, and what are the datatypes of the PL/SQL variables?
-- Brian
Hello,
We have downloaded JDev 903 Preview to try out the new PL/SQL debugging features, but it seems we are unable to inspect/watch/debug PL/SQL variables. The relevant panels are simply blank.
Strangely enough, the help files are also lacking on the subject (e.g. the "About debugging PL/SQL" help topic does not seem to exist).
Is there an option to turn on in the database server to view PL/SQL variables ?
Thanks
Regards
Brice

My problem in Weblogic and Message Driven Bean for Topic

Hello to all
I used this page (http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
for setup JMS Server, Queue, Connection Factory on Weblogic Server
and I created a Message Driven Bean ,I used those Queue , and all things was OK
But I wanted to setup a Topic and use it in this manner
I created a Topic like previous steps for setup Queue
(http://www.ecomputercoach.com/index.php/component/content/article/90-weblogic-jms-queue-setup.html?showall=1)
Except in Step 3 ,I selected Topic instead of Queue
then I created a Message Driven Bean in JDeveloper , my Message Driven Bean is like this:
@MessageDriven(mappedName = "jndi.testTopic")
<p>
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
</p>
When I deploy the Application , Weblogic shows me this error:
+<Aug 30, 2011 11:32:28 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: aliJMS1_MessageDrivenEJBBean is unable to connect to th+
e JMS destination: jndi.testTopic. The Error was:
+[EJB:011011]The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: jndi.testTopic. However, the object with+
the JNDI name: jndi.testTopic is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).>
And when I send message to the topic The Message Dirven Bean dosen't work
But when I create an ordinary Java application like this (it uses that Tpoic) :
import java.io.*;
import java.util.*;
import javax.transaction.*;
import javax.naming.*;
import javax.jms.*;
public class TopicReceive implements MessageListener
    public final static String JNDI_FACTORY =
        "weblogic.jndi.WLInitialContextFactory";
    public final static String JMS_FACTORY =
        "jndi.testConnectionFactory";
    public final static String TOPIC = "jndi.testTopic";
    private TopicConnectionFactory tconFactory;
    private TopicConnection tcon;
    private TopicSession tsession;
    private TopicSubscriber tsubscriber;
    private Topic topic;
    private boolean quit = false;
    public void onMessage(Message msg) {
        try {
            String msgText;
            if (msg instanceof TextMessage) {
                msgText = ((TextMessage)msg).getText();
            } else {
                msgText = msg.toString();
            System.out.println("JMS Message Received: " + msgText);
            if (msgText.equalsIgnoreCase("quit")) {
                synchronized (this) {
                    quit = true;
                    this.notifyAll();
        } catch (JMSException jmse) {
            jmse.printStackTrace();
    public void init(Context ctx, String topicName) throws NamingException,
                                                           JMSException {
        tconFactory = (TopicConnectionFactory)ctx.lookup(JMS_FACTORY);
        tcon = tconFactory.createTopicConnection();
        tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        topic = (Topic)ctx.lookup(topicName);
        tsubscriber = tsession.createSubscriber(topic);
        tsubscriber.setMessageListener(this);
        tcon.start();
    public void close() throws JMSException {
        tsubscriber.close();
        tsession.close();
        tcon.close();
    public static void main(String[] args) throws Exception {
        InitialContext ic = getInitialContext("t3://127.0.0.1:7001");
        TopicReceive tr = new TopicReceive();
        tr.init(ic, TOPIC);
        System.out.println("JMS Ready To Receive Messages (To quit, send a \"quit\" message).");
        synchronized (tr) {
            while (!tr.quit) {
                try {
                    tr.wait();
                } catch (InterruptedException ie) {
        tr.close();
    private static InitialContext getInitialContext(String url) throws NamingException {
        Hashtable env = new Hashtable();
        env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
        env.put(Context.PROVIDER_URL, url);
        env.put("weblogic.jndi.createIntermediateContexts", "true");
        return new InitialContext(env);
It's OK and shows messages When I send message to the Topic
Now I want know why the Message Driven Bean doesn't work for those Topic
I want create a Message Driven Bean for Topic in the same way I created for Queue
I don't know what is problem , please advice me
Thanks

Could you try adding a activationconfig to the message-driven bean, for example,
@MessageDriven(mappedName = "jndi.testTopic", activationConfig = {
        @ActivationConfigProperty(propertyName = "destinationName", propertyValue = "jndi.testTopic"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic")
public class aliJMS1_MessageDrivenEJBBean implements MessageListener {
    public void onMessage(Message message) {
      if(message instanceof TextMessage ){
        TextMessage txtM=(TextMessage) message;
        try{
          System.out.println(txtM.getText());
        }catch(Exception ex){
          ex.printStackTrace();
}

Best way to call web service from Message Driven Bean

I'm q'ing msgs up and would like to use a message driven bean to forward them to
an external web service. Weblogic workshop does not seem to support web service
controls in an EJB project. Any suggestions?
Thanks,
Paul

Paul,
A non-trivial alternative, since you have the WSDL, would be to forget about trying
to use generated client code and just use JAX-RPC dynamic invocation instead.
That's how I call external web services from within an EJB in situations in which
generated client code cannot be incorporated prior to deployment. Minimally all
that is required is the WSDL and the service name, port name, and operation name,
although if non-builtin parameter types are used then you will have to manipulate
the service's type mapping registry.
Mark
"Paul" <[email protected]> wrote:
>
I've taken our wsdl and generated a web service in Workshop 8.1 using
XMLBeans.
This produces a web page that contains a link"Java Proxy" for downloading
generated
client code. I assume this is the same as clientgen. It's interesting
that
it does not
use XMLBeans like the web service that generated it. It uses a different
serialization
method.
I've used this generated code to call the web service. Although the
client seems
to run
successfully to completion, I get the following error in the weblogic
server console:
<Sep 29, 2003 7:46:24 AM EDT> <Error> <WLW> <000000> <Failure=com.bea.wlw.runtim
e.core.request.ResponseValidationException: java.lang.RuntimeException:
Protocol
'http-soap' not available on this operation. [ServiceException]>
<Sep 29, 2003 7:46:24 AM EDT> <Warning> <WLW> <000000> <Returning HTTP
500 due
t
o SOAP fault occurring on DispFile=pjm.srcm.webservices.face.Receptor>
Frustrating...
Bruce Stephens <[email protected]> wrote:
Hi Paul,
Could you not first use clientgen on the external webservice, then take
the stubs it created, then add these to your code along with the
onMessage(Message msg) and roll it into the MBean?
We don't have exactly that example, but you might take a look at this
one to get some ideas:
http://webservice.bea.com/message.zip
Hope this helps,
Bruce
Paul wrote:
Bruce,
Don't think this will work for us. We are receiving data internallythrough
a JMS queue. We need to pull it off the queue (MDB), massage it alittle and
send it to an external web service. The link you sent me was howto implement
a web service with JMS.
I started out by trying to use the Web Service and JMS controls butit doesn't
seem like I can use a JMS control because that requires a conversationID,
which we don't have because nothing is comming in through a web services.
Paul
Bruce Stephens <[email protected]> wrote:
Hi Paul,
There is a chapter in the docs on this. See if this helps,
http://edocs.bea.com/wls/docs81/webserv/jms.html#1067060
Thanks,
Bruce
Paul wrote:
I'm q'ing msgs up and would like to use a message driven bean to
forward
them to
an external web service. Weblogic workshop does not seem to supportweb service
controls in an EJB project. Any suggestions?
Thanks,
Paul

SONIC MQ - Message Driven Bean with CMT

Hi guys,
I am having hard time with MDB having container managed transaction with TX attribute required. I am using RAD 6.0.1 and the JMS provider is Sonic MQ.I have defined XAConnectionFactory on Sonic side. The MDB runs without any error, but when I shut down the app server the message appears back in the queue. When I use transaction attribute as NOT SUPPORTED everything runs as normal.
Am I missing something on the configuration here?
I am seeing the XA implementation classes in the sonic jar file, but do I need their resource adaptor from sonic?
Thanks
Matt

The current version of the white-paper that Raffi
          refers to covers through 7.0. For 8.1 see also
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          and
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html
          these features can often make integration easier.
          Tom
          Raffi wrote:
          > Doug,
          >
          > You can find very detailed information on this topic at the link below. All
          > you need to do is specify the destination-jndi-name, initial-context-factory,
          > provider-url, and connection-factory-jndi-name in weblogic-ejb-jar.xml for the
          > non-BEA JMS provider for that specific MDB.
          >
          > ftp://edownload:[email protected]/pub/downloads/jmsproviders.pdf
          >
          > Hope that helps!
          >
          > Raffi
          >
          > Doug Chew <[email protected]> wrote:
          >
          >>Can someone give me an example on how to setup a message driven bean
          >>with a foreign JMS provider using the foreign JMS provider's implementation
          >>of a connection factory. i.e. binding the foreign JMS provider's connection
          >>factory to the JNDI tree.
          >>
          >>Thanks
          >
          >

Error while deploying a message driven bean

I am deployeing a MDB which is done successfully but the message is not retrieved(No message in teh queue). The following description is given in the log file.
#1.5#0016E6197593004B0000000B000013040004288DE20D6CD8#1170489754872#com.sap.security.core.policy.PolicyInfoManagerImpl##com.sap.security.core.policy.PolicyInfoManagerImpl.copyApplicationConfiguration#Administrator#523####e5dbec01b35c11db90e70016e6197593#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occured while copying configurations for application . Reason: #3#sap.com/MessageEAR#com.sap.engine.frame.core.configuration.NameNotFoundException#A configuration with the path "webservices/services/sap.com/MessageEAR" does not exist.#
Can you please tell where to look for it and what to do?

the session bean is ::
public class SenderBean implements SessionBean {
public static final boolean DEBUG = false;
private SessionContext ctx;
private TopicConnectionFactory factory;
private TopicConnection connection;
private Topic topic;
public SenderBean() {
     log("constructor");
public void ejbCreateSender() throws CreateException {
     log("ejbCreate");
            try {
               InitialContext naming = new InitialContext();
               factory = (TopicConnectionFactory)naming.lookup("jmsfactory/default/ExceptionTopicFactory");
               topic = (Topic)naming.lookup("jmstopics/default/ExceptionTopic");
               log("factory: " + factory);
               allocateResources();
            } catch (Exception exc) {
               log("exception occured during ejbCreate().");
               throw new CreateException("Unexpected exception in ejbCreate().");
public void ejbCreate() throws CreateException {
public void ejbActivate() {
     log("ejbActivate");
     try {
       allocateResources();
     } catch (Exception exc) {
       exc.printStackTrace();
public void ejbPassivate() {
     log("ejbPassivate");
     try {
       releaseResources();
     } catch (Exception exc) {
       exc.printStackTrace();
public void ejbRemove() {
     log("ejbRemove");
public void setSessionContext(SessionContext _ctx) {
     log("setSessionContext");
     ctx = _ctx;
public void sendMessage(String text) throws MessageNotSentException {
     log("sendMessage");
     log("text = " + text);
     TopicSession session = null;
     try {
       session = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
       log("topic = " + topic);
       TopicPublisher publisher = session.createPublisher(topic);
       TextMessage textMessage = session.createTextMessage();
       textMessage.setText(text);
       publisher.publish(textMessage);
       System.out.println("Message Sent");
       log("message sent");
     } catch (JMSException jmse) {
       jmse.printStackTrace();
       throw new MessageNotSentException(jmse.toString());
     } finally {
       try {
          if (session != null) {
            session.close();
       } catch (Exception exc) {
private void releaseResources() throws JMSException {
     connection.close();
     connection = null;
private void allocateResources() throws JMSException {
     connection = factory.createTopicConnection();
     log("connection = " + connection);
     connection.start();
     log("connection started");
private void log(String message) {
     if (DEBUG) {
       System.out.println("SenderBean: " + message);
the mdb is::
public class MessageDisplayBean implements MessageDrivenBean, MessageListener {
       public static final boolean DEBUG = false;
       private MessageDrivenContext ctx;
       private QueueConnectionFactory factory;
       private QueueConnection connection;
       private Queue queue;
       public MessageDisplayBean() {
          System.out.println("In constructor");
          log("constructor");
       public void onMessage(Message message) {
          TextMessage textMessage = (TextMessage)message;
          try {
            String text = textMessage.getText();
            log("message received. Text follows:\n\n " + text + "\n\n");
            connection = factory.createQueueConnection();
            connection.start();
            QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
            TextMessage confirmation = session.createTextMessage();
            confirmation.setText("Message \""+ textMessage.getText() + "\" received.");
            //queue = session.createQueue("ConfirmationQueue");
            QueueSender sender = session.createSender(queue);
            sender.send(confirmation);
            session.close();
            connection.close();
            System.out.println("Message received");
          } catch (javax.jms.JMSException jmse) {
       public void ejbRemove() {
          log("ejbRemove()");
       public void setMessageDrivenContext(MessageDrivenContext _ctx) {
          log("setMessageDrivenContext()");
          ctx = _ctx;
          System.out.println("In context");
       public void ejbCreate() {
          try {
               System.out.println("In ejbcreate");
            InitialContext naming = new InitialContext();
            factory = (QueueConnectionFactory)naming.lookup("jmsfactory/default/ExceptionQueueFactory");
            queue = (Queue)naming.lookup("jmsqueues/default/ExceptionQueue");
            log("factory: " + factory);
          } catch (Exception exc) {
            log("exception occured during ejbCreate().");
          log("ejbCreate()");
       private void log(String str) {
          if (DEBUG) {
            System.out.println("MessageDisplayBean: " + str);
th ejb-j2ee-engine.xml is::
<ejb-j2ee-engine>
     <enterprise-beans>
          <enterprise-bean>
               <ejb-name>MessageDisplayBean</ejb-name>
               <jndi-name>MessageDisplayBean</jndi-name>
               <message-props>
                    <destination-name>ExceptionTopic</destination-name>
                    <connection-factory-name>ExceptionTopicFactory</connection-factory-name>
               </message-props>
          </enterprise-bean>
          <enterprise-bean>
               <ejb-name>MessageSender</ejb-name>
               <jndi-name>MessageSender</jndi-name>
               <session-props/>
          </enterprise-bean>
               </enterprise-beans>
</ejb-j2ee-engine>
the ejb-jar.xml is::
             <ejb-jar>
    <display-name>        Message Driver Bean Example      </display-name>
    <enterprise-beans>
        <session>
            <display-name>            MessageSender          </display-name>
            <ejb-name>MessageSender</ejb-name>
            <home>com.sap.message.sender.SenderHome</home>
            <remote>com.sap.message.sender.Sender</remote>
            <local-home>com.sap.message.sender.SenderLocalHome</local-home>
            <local>com.sap.message.sender.SenderLocal</local>
            <ejb-class>com.sap.message.sender.SenderBean</ejb-class>
            <session-type>Stateful</session-type>
            <transaction-type>Container</transaction-type>
            <ejb-local-ref>
                <ejb-ref-name>ejb/SenderBean</ejb-ref-name>
                <ejb-ref-type>Session</ejb-ref-type>
                <local-home>com.sap.message.sender.SenderLocalHome</local-home>
                <local>com.sap.message.sender.SenderLocal</local>
                <ejb-link>MyEJB.jar#MessageSender</ejb-link>
            </ejb-local-ref>
            <resource-ref>
                <res-ref-name>ExceptionTopicFactory</res-ref-name>
                <res-type>javax.jms.TopicConnectionFactory</res-type>
                <res-auth> Container</res-auth>
            </resource-ref>
            <resource-env-ref>
                <resource-env-ref-name>ExceptionTopic        </resource-env-ref-name>
                <resource-env-ref-type>   javax.jms.Topic        </resource-env-ref-type>
            </resource-env-ref>
        </session>
        <message-driven>
            <ejb-name>MessageDisplayBean</ejb-name>
            <ejb-class>com.sap.message.mdb.MessageDisplayBean</ejb-class>
            <transaction-type>Container</transaction-type>
            <message-driven-destination>
                <destination-type>javax.jms.Topic</destination-type>
            </message-driven-destination>
            <resource-ref>
                <res-ref-name>   ExceptionQueueFactory            </res-ref-name>
                <res-type>              javax.jms.QueueConnectionFactory            </res-type>
                <res-auth>              Container            </res-auth>
            </resource-ref>
            <resource-env-ref>
                <resource-env-ref-name>        ExceptionQueue        </resource-env-ref-name>
                <resource-env-ref-type>          javax.jms.Queue        </resource-env-ref-type>
            </resource-env-ref>
        </message-driven>
           </enterprise-beans>
    <assembly-descriptor>
        <container-transaction>
            <method>
                <ejb-name>MessageDisplayBean</ejb-name>
                <method-name>onMessage</method-name>
            </method>
                      <trans-attribute>           NotSupported         </trans-attribute>
        </container-transaction>
    </assembly-descriptor>
</ejb-jar>

WebLogic 10 and EJB 3.0 for Message Driven Bean

Hi,
I am trying to deploy Message Driven Bean using EJB3.0 on weblogic 10. I am using annotations and don't want to use deployment descriptors.
The Bean class:
CalculatorBean.java
import javax.ejb.*;
import javax.jms.*;
import java.sql.Timestamp;
import java.util.StringTokenizer;
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/mdb")
public class CalculatorBean implements MessageListener {
public void onMessage (Message msg) {
TextMessage tmsg=null;
try {
if (msg instanceof TextMessage) {
tmsg = (TextMessage) msg;
System.out.println
("MESSAGE BEAN1: Message received: "
+ tmsg.getText());
} else {
System.out.println
("Message of wrong type1: "
+ msg.getClass().getName());
catch (JMSException e) {
e.printStackTrace();
catch (Throwable te) {
te.printStackTrace();
My client:
import javax.naming.*;
import javax.naming.InitialContext;
import java.text.*;
import javax.jms.*;
public class MsgClient {
public static void main(String args[])
QueueConnection cnn=null;
QueueSender sender=null;
QueueSession sess=null;
Queue queue=null;
try {
java.util.Properties p = new java.util.Properties();
p.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
p.put("java.naming.provider.url","t3://10.6.74.79:7001");
Context ctx=new InitialContext(p);
//InitialContext ctx=new InitialContext(p);
queue = (Queue)ctx.lookup("queue/mdb");
QueueConnectionFactory factory = (QueueConnectionFactory)ctx.lookup("ConnectionFactory");
cnn = factory.createQueueConnection();
sess= cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
sender = sess.createSender(queue);
TextMessage message = sess.createTextMessage();
message.setText("This is message by Gurumurthy" );
System.out.println("Sending message: " +message.getText());
sender.send(message);
sess.close();
catch (Exception e)
e.printStackTrace();
I am compiling and creating jar file for this class. Then I am creating a .ear file for this.
The meta-inf/application.xml contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com /xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
<display-name>MDBWorking1</display-name>
<description>Application description</description>
<module>
<ejb>MDBWorking1.jar</ejb>
</module>
</application>
I don't want to use deployment descriptor (ejb-jar.xml or weblogic-ejb-jar-xml), because I want to utilize the annotation feature of EJB3.0
So, after creating the .ear file for this, and try to deploy on weblogic 10, I get the following error:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(MDBWorking1.jar) Unable to deploy EJB: CalculatorBean from MDBWorking1.jar: [EJB:011113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
Substituted for missing class [EJB - 11113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
How to solve this?
Note:
I don't want to use Deployment Descriptor and all I want to use is EJB3.0's annotation feature.
Thanks,
Guru

Dear gurubbc,
I don't know if it still matters to you but you can use the javax.ejb.MessageDriven annotation to point your bean on your queue. I had the same issue like you but i could not solve it properly by switchihg to weblogic.ejb.MessageDriven.
Use the following annotation and it should work out:
@MessageDriven
(mappedName = "queue/mdb",
name = "CalculatorBean",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
Here you can see that the mappedName is the JNDI name of the queue you are trying to connect to. The name is the name for your Bean, and the only property passed is the destination type.
Hope this helps.
Cheers,
Istvan

JBoss message driven bean calling a session bean

Hi guys, can you please help me? I want my mdb to call my session bean....can you provide me some examples of ejb-jar.xml and jboss.xml with regards to this configuration....thanks...im creating my deployment descriptors manually

Here is a little example, I hope it will help you.
ejb-jar.xml
=============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<enterprise-beans>

<session >
<display-name>TestSessionEJB</display-name>
<ejb-name>TestSession</ejb-name>
<home>mdbtest.interfaces.TestSessionHome</home>
<remote>mdbtest.interfaces.TestSession</remote>
<local-home>mdbtest.interfaces.TestSessionLocalHome</local-home>
<local>mdbtest.interfaces.TestSessionLocal</local>
<ejb-class>mdbtest.session.TestSessionEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
... </session>

<message-driven >
<description><![CDATA[]]></description>
<display-name>TestMessageEJB</display-name>
<ejb-name>TestMessage</ejb-name>
<ejb-class>mdbtest.message.TestMessageEJB</ejb-class>
<transaction-type>Container</transaction-type>
<message-selector></message-selector>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<ejb-local-ref >
<ejb-ref-name>ejb/TestEjb</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>mdbtest.interfaces.TestSessionLocalHome</local-home>
<local>mdbtest.interfaces.TestSessionLocal</local>
<ejb-link>TestSession</ejb-link>
</ejb-local-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
jboss.xml:
=============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>TestSession</ejb-name>
<jndi-name>ejb/MdbTest/TestSession</jndi-name>
<local-jndi-name>TestSessionLocal</local-jndi-name>
<configuration-name>Standard Stateless SessionBean</configuration-name>
</session>
<message-driven>
<ejb-name>TestMessage</ejb-name>
<destination-jndi-name>queue/MyTestQueue</destination-jndi-name>
<configuration-name>Standard Message Driven Bean</configuration-name>
</message-driven>
</enterprise-beans>
<resource-managers>
</resource-managers>
</jboss>

Unable to download an Message Driven Bean Example

Similar Messages

Maybe you are looking for