Create EJB 3.0 Message Driven Bean on a Oracle JMS (AQ)

Hi, I need to develop a EJB 3.0 Message Driven Bean. The MDB has to work on a Oracle AQ using Oracle JMS. Is there any how-to document giving an example about this issue. Can you give an example how to create the JMS destination in OC4J (how to configure the Oracle JMS AQ in OC4j), issue the JMS destination via annotions (resource injection) in the MDB. Please give me a working example of the MDB and a test client to produce a message. Regards, Arjan Jorritsma

Check your ejb-jar.xml and see if it has the version of "2.1" there...
If the application was depending upon EJB 3.0 annotations but it had a ejb-jar.xml that had version set to "2.1" and there was no oracle specific descriptor (orion-ejb-jar.xml) to designate it use the resource adapter; It would expect JMS destination and connection factory that is required for a JMS-MDB set in the ejb-jar.xml. So try to change the ejb-jar.xml to update the version to "3.0", OC4J would have parsed the annotation and combined the metadata with ejb-jar.xml and it would work.
-Frances

Similar Messages

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 deployment error

Hi:
When attempting to deploy a message-driven bean to the server I get a the following error message:SEVERE: MDB00030: [MessageControllerJAR:MessageControllerEJB]: Exception in setting up message-drive
n bean container: [[C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatEx
ception] However, bindings to the queues seem to be created successfully, as evidenced here:
INFO: CORE5076: Using Java HotSpot(TM) Server VM, Version 1.4.2_02 from Sun Microsystems Inc.
INFO: JTS5014: Recoverable JTS instance, serverId is 100
INFO: RAR5060: Install JDBC Datasources ...
INFO: JMS5015: Install JMS resources ...
INFO: JMS5002: Binding [< JMS Destination: jms/Sample, javax.jms.Queue, [ imqDestinationName=sample] >]
INFO: JMS5002: Binding [< JMS Connection Factory: jms/SampleQCF, javax.jms.QueueConnectionFactory [imqBrokerHostName=localhost , imqBrokerHostPort=7222 ] >]
INFO: LDR5010: All ejb(s) of [stateless-simple] loaded successfully!
INFO: WEB0100: Loading web module [stateless-simple:stateless-simple.war] in virtual server [server1
] at [helloworld]
INFO: HTTP3072: HTTP listener http-listener-1 [http://xxxxxx:99] ready to accept requests
startup: server started successfully
INFO: CORE3274: successful server startup
I'm using an external JMS provider and according to them the problem is not their server. If we look at the exception trace (javax.jms.JMSException) this is what gets displayed in the server's console:
SEVERE: MDB00030: [MessageControllerJAR:MessageControllerEJB]: Exception in setting up message-drive
n bean container: [[C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatEx
ception]
SEVERE: MDB00017: [MessageControllerEJB]: Exception in creating message-driven bean container: [java
x.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatE
xception]
SEVERE: javax.jms.JMSException
javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFor
matException
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
        at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
        at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
        at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection(ConnectionFactoryWrapper.java:118)
        at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:394)
        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.EJBModuleLoader.load(EJBModuleLoader.java:79)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
        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
SEVERE: EJB5090: Exception in creating EJB container [javax.jms.JMSException: [C4003]: Error occurre
d on connection creation. - caught java.lang.NumberFormatException]
SEVERE: appId=MessageControllerJAR moduleName=MessageControllerJAR ejbName=MessageControllerEJB
SEVERE: LDR5004: UnExpected error occured while creating ejb container
javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFor
matException
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
        at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
        at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
        at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection(ConnectionFactoryWrapper.java:118)
        at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:394)
        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.EJBModuleLoader.load(EJBModuleLoader.java:79)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
        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.ja
WARNING: CORE5020: Error while loading ejb module
WARNING: ADM5603:Event listener error [Error while loading EJB module [MessageControllerJAR]. Please refer to the server log for more details. Any suggestions will be appreciated. Thanks. SC

Hi:
When attempting to deploy a message-driven bean to the server I get a the following error message:SEVERE: MDB00030: [MessageControllerJAR:MessageControllerEJB]: Exception in setting up message-drive
n bean container: [[C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatEx
ception] However, bindings to the queues seem to be created successfully, as evidenced here:
INFO: CORE5076: Using Java HotSpot(TM) Server VM, Version 1.4.2_02 from Sun Microsystems Inc.
INFO: JTS5014: Recoverable JTS instance, serverId is 100
INFO: RAR5060: Install JDBC Datasources ...
INFO: JMS5015: Install JMS resources ...
INFO: JMS5002: Binding [< JMS Destination: jms/Sample, javax.jms.Queue, [ imqDestinationName=sample] >]
INFO: JMS5002: Binding [< JMS Connection Factory: jms/SampleQCF, javax.jms.QueueConnectionFactory [imqBrokerHostName=localhost , imqBrokerHostPort=7222 ] >]
INFO: LDR5010: All ejb(s) of [stateless-simple] loaded successfully!
INFO: WEB0100: Loading web module [stateless-simple:stateless-simple.war] in virtual server [server1
] at [helloworld]
INFO: HTTP3072: HTTP listener http-listener-1 [http://xxxxxx:99] ready to accept requests
startup: server started successfully
INFO: CORE3274: successful server startup
I'm using an external JMS provider and according to them the problem is not their server. If we look at the exception trace (javax.jms.JMSException) this is what gets displayed in the server's console:
SEVERE: MDB00030: [MessageControllerJAR:MessageControllerEJB]: Exception in setting up message-drive
n bean container: [[C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatEx
ception]
SEVERE: MDB00017: [MessageControllerEJB]: Exception in creating message-driven bean container: [java
x.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFormatE
xception]
SEVERE: javax.jms.JMSException
javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFor
matException
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
        at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
        at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
        at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection(ConnectionFactoryWrapper.java:118)
        at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:394)
        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.EJBModuleLoader.load(EJBModuleLoader.java:79)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
        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
SEVERE: EJB5090: Exception in creating EJB container [javax.jms.JMSException: [C4003]: Error occurre
d on connection creation. - caught java.lang.NumberFormatException]
SEVERE: appId=MessageControllerJAR moduleName=MessageControllerJAR ejbName=MessageControllerEJB
SEVERE: LDR5004: UnExpected error occured while creating ejb container
javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught java.lang.NumberFor
matException
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(ExceptionHandler.java:183)
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(ExceptionHandler.java:136)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:145)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:86)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:47)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:46)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:101)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:501)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:930)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1482)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:403)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:234)
        at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
        at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXAQueueConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
        at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.createXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
        at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection(ConnectionFactoryWrapper.java:118)
        at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:394)
        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.EJBModuleLoader.load(EJBModuleLoader.java:79)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:194)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:166)
        at com.iplanet.ias.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:297)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:464)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:451)
        at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:294)
        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.ja
WARNING: CORE5020: Error while loading ejb module
WARNING: ADM5603:Event listener error [Error while loading EJB module [MessageControllerJAR]. Please refer to the server log for more details. Any suggestions will be appreciated. Thanks. SC

Dynamic queue listener in Message driven bean

Hi all
I wonder if exists a way for creating a message driven bean that reads messages from a queue defined on fly.
I mean I'd like to create an mdb that read from queue ,where the queue name is defined in a data base table .
Hope to be clear.
Thanks in advance

Yes, you can use either a queue or a topic to drive an MDB.
There are a number of discussion threads related to MDB's in
weblogic.develoepr.interest.jms.
"Herman Lam" <[email protected]> wrote in message
news:3ac891da$[email protected]..
>
Hi Folk:
Does anyone know whether the Weblogic 6.0 EJB 2.0 Message Driven Bean cansupport
queue event for the OnMessage( javax.jms.Message messagenmae)
callback method or does it only support publisher/subscriber event ?
Best Regards
Herman

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

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
          >
          >

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
          >
          >

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

Creating a Message-Driven Bean in 10.1.3

I have been trying to create a Message-Driven Bean using the wizard but when I tried to deploy it to the stand-alone OC4J, I always got the null pointer exception:
Caused by: java.lang.NullPointerException
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:227)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:199)
at com.evermind.server.ejb.deployment.EJBPackage.parseOrionAssemblyDescriptor(EJBPackage.java:973)
I am using EJB 2.1, the default jms/QueueConnectionFactory and jms/demoQueue.
I have been trying to find some simple examples and tutorials to do it but have been unsuccessful. Could somebody please point me to the right direction?

After spending many hours reading the documentation, I have finally created a MDB that works. The original problem was due to the wizard not updating the orion-ejb-jar.xml file. This I had to do manually.
I am now trying to use this MDB to process a JMS Web Service, created by using the Web Service wizard. I use the demoQueue for the send operation and demoTopic for the receive operation. I could only get this to work provided I generated a J2EE 1.3 (Oracle) Web Service. If I generated a J2EE 1.4 (JAX-RPC), I had two problems:
1. If I only filled in the send but not the receive details, an error saying cannot locate the JMS resource was returned when I called a send operation. I shouldn't need to fill in the receive details as I was only trying to issue a send call.
2. If I also filled in the receive details, then the send request hanged.
In both cases, I could not see my MDB being activated.
If I switched to J2EE 1.3 option, then both the send and receive operations would work.
Could anybody give me any advices?

Message driven bean: resource not created

Hi,
I'm having trouble deploying a simple test app that I've created (in App Server Platform Edition 8.0). It contains a servlet, that posts messages to a queue, and which appears to work fine. There is also a message-driven bean that receives these messages, but it will not deploy as is. I would be grateful for any assistance in working out why. Apologies if I'm missing something obvious, but the technology is quite new to me.
I get the following error in the server log -
[#|2004-07-14T14:03:49.640+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=12;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : joeMDB]|#]
[#|2004-07-14T14:03:49.656+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=12;|appId=mdbtest moduleName=ejb-jar-ic_jar ejbName=joeMDB|#]
[#|2004-07-14T14:03:49.656+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=12;|LDR5004: UnExpected error occured while creating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : joeMDB
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:296)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:232)
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:189)
- which I can't find referenced in any other forum post. The relevant deployment descriptors are as follows -
ejb-jar.xml -
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1" 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/ejb-jar_2_1.xsd">
<display-name>mdbJar</display-name>
<enterprise-beans>
<message-driven>
<ejb-name>joeMDB</ejb-name>
<ejb-class>joeMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-link>jms/JoeDestQueue</message-destination-link>
<message-destination-ref>
<message-destination-ref-name>jmsJoeDestQueue</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Consumes</message-destination-usage>
<message-destination-link>jms/JoeDestQueue</message-destination-link>
</message-destination-ref>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>joeMDB</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<message-destination>
<message-destination-name>jms/JoeDestQueue</message-destination-name>
</message-destination>
</assembly-descriptor>
</ejb-jar>
sun-ejb-jar.xml -
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.0 EJB 2.1//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-0.dtd">
<sun-ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee">
<enterprise-beans>
<unique-id>0</unique-id>
<ejb>
<ejb-name>joeMDB</ejb-name>
<jndi-name>joeMDB</jndi-name>
<pass-by-reference>false</pass-by-reference>
<mdb-connection-factory>
<jndi-name>jms/joeFactory</jndi-name>
</mdb-connection-factory>
<jms-max-messages-load>1</jms-max-messages-load>
<is-read-only-bean>false</is-read-only-bean>
<refresh-period-in-seconds>-1</refresh-period-in-seconds>
<cmt-timeout-in-seconds>0</cmt-timeout-in-seconds>
<gen-classes/>
<bean-pool>
<steady-pool-size>-1</steady-pool-size>
<resize-quantity>-1</resize-quantity>
<max-pool-size>-1</max-pool-size>
<pool-idle-timeout-in-seconds>-1</pool-idle-timeout-in-seconds>
<max-wait-time-in-millis>-1</max-wait-time-in-millis>
</bean-pool>
</ejb>
<message-destination>
<message-destination-name>jms/JoeDestQueue</message-destination-name>
<jndi-name>jms/JoeDestQueue</jndi-name>
</message-destination>
</enterprise-beans>
</sun-ejb-jar>
Thanks,
Joe

Hi, Joe,
The message says that
JMS resource not created : joeMDB
The command to add the missing Queue:
asadmin create-jms-resource user admin restype javax.jms.Queue JoeDestQueue
Please note:
in your sun-ejb-jar.xml, the real JNDI name for the Queue is JoeDestQueue.
Double check the namings for the Queue in both ejb-jar.xml and sun-ejb-jar.xml.
You only need two names for one Queue: one is for JNDI, one is for reference.
_Dianne

Creating Message Driven Bean

When will JDeveloper have support for Message Driven Beans? A search of the JDeveloper help on the subject found nothing.
In the meantime, is there a work-around that you can suggest for working with Message-Driven Beans in JDeveloper?
Thanks in advance for your help.

Oracle9i JDeveloper (9.0.3) which is the next release will have support for EJB 2.0 including Message Driven Beans.
This release is slated for this summer.
raghu
JDev Team

How to transaction in the message driven bean?

          hello
          i write a message driven bean,that monitor the weblogic message queue,when a "Order"
          object is witten to the queue,the mdb get it and write it to a entity bean "Orderinfo".all
          of above logic is within the "onMessage" method of the mdb.
          i want to encapsulate the flow in a transaction,see my code snippet of the onMessage
          method:
          ObjectMessage objMsg = (ObjectMessage) msg;
          OrderVO orderVO = (OrderVO) objMsg.getObject();
          System.out.println(orderVO.booklist);
          OrderinfoHome orderinfoHome = (OrderinfoHome) ctx.lookup(
          "java:/comp/env/orderinfo");
          Orderinfo orderinfo = orderinfoHome.create(orderVO.orderID);
          orderinfo.setAddress(orderVO.address);
          orderinfo.setCustname(orderVO.custName);
          orderinfo.setEmail(orderVO.email);
          orderinfo.setBooklist(orderVO.booklist);
          orderinfo.setPrice(new BigDecimal(orderVO.price));
          and deploy descriptor snippet(ejb-jar.xml):
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>orderMDB</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          i think during this transaction,there are two action:geting the object from the
          queue and saving it to entity bean.in order to test the transaction,i modify the
          jndi name of entity bean in the code to a WRONG one.redeploy my program,and send
          a message to the queue,the mdb is activated,then the exception is thrown because
          of the wrong jndi name.after that,i check the message queue,find that it is empty.why?i
          think if the second action of the transaction is fail,the transaction should roll
          back,the message should be send BACK to the queue.
          i also ty to use the "javax.transaction.UserTransaction" in the onMessage method,but
          the follwing exception is thrown:
          javax.transaction.NotSupportedException: Another transaction is associated with
          this thread.................................
          who can help me,if any wrong with me,and how to use the transaction with the message
          driven bean?
          thank you.


The transaction should rollback if the MDB throws an
          exception. Try changing your MDB code to
          call "setRollbackOnly()" on the EJB
          context (instead of throwing an exception) to see
          if that works. If calling "setRollbackOnly()" fixes
          the problem - then please contact customer support
          and report a bug.
          zbcong wrote:
          > hello
          >
          > i write a message driven bean,that monitor the weblogic message queue,when a "Order"
          > object is witten to the queue,the mdb get it and write it to a entity bean "Orderinfo".all
          > of above logic is within the "onMessage" method of the mdb.
          > i want to encapsulate the flow in a transaction,see my code snippet of the onMessage
          > method:
          >
          >
          > ObjectMessage objMsg = (ObjectMessage) msg;
          > OrderVO orderVO = (OrderVO) objMsg.getObject();
          > System.out.println(orderVO.booklist);
          > OrderinfoHome orderinfoHome = (OrderinfoHome) ctx.lookup(
          > "java:/comp/env/orderinfo");
          > Orderinfo orderinfo = orderinfoHome.create(orderVO.orderID);
          > orderinfo.setAddress(orderVO.address);
          > orderinfo.setCustname(orderVO.custName);
          > orderinfo.setEmail(orderVO.email);
          > orderinfo.setBooklist(orderVO.booklist);
          > orderinfo.setPrice(new BigDecimal(orderVO.price));
          >
          >
          > and deploy descriptor snippet(ejb-jar.xml):
          >
          >
          > <assembly-descriptor>
          > ............
          > ...........
          >
          > <container-transaction>
          > <method>
          > <ejb-name>orderMDB</ejb-name>
          > <method-name>*</method-name>
          > </method>
          > <trans-attribute>Required</trans-attribute>
          > </container-transaction>
          > </assembly-descriptor>
          >
          >
          > i think during this transaction,there are two action:geting the object from the
          > queue and saving it to entity bean.in order to test the transaction,i modify the
          > jndi name of entity bean in the code to a WRONG one.redeploy my program,and send
          > a message to the queue,the mdb is activated,then the exception is thrown because
          > of the wrong jndi name.after that,i check the message queue,find that it is empty.why?i
          > think if the second action of the transaction is fail,the transaction should roll
          > back,the message should be send BACK to the queue.
          >
          > i also ty to use the "javax.transaction.UserTransaction" in the onMessage method,but
          > the follwing exception is thrown:
          >
          > javax.transaction.NotSupportedException: Another transaction is associated with
          > this thread.................................
          >
          > who can help me,if any wrong with me,and how to use the transaction with the message
          > driven bean?
          >
          > thank you.
          >
          >

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>

Message Driven Bean: problem with @RunAs annotation

I am having a problem using the @RunAs annotation in a message driven bean.
I would like the code in my onMessage() method to be executed with a specific role/user, so I want to use the @RunAs annotation to achieve this.
I am running weblogic 10.0.
I have created the following in weblogic console:
- Group "TestGroup"
- User "TestUser", member of "TestGroup"
- Global Role "TestRole", role condition: "Group : TestGroup"
The MDB:
package be.cegeka.test.mdb;
import javax.annotation.Resource;
import javax.annotation.security.RunAs;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.jms.MessageListener;
@MessageDriven(
          mappedName = "testQueue",
          name = "TestMDB",
          activationConfig = {
                    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
@RunAs("TestRole")
public class TestMDB implements MessageListener {
     @Resource
     private MessageDrivenContext mdContext;
      * {@inheritDoc}}
     public void onMessage(Message msg) {
          System.out.println("Handling message for user "
                    + mdContext.getCallerPrincipal().getName());
}[u]The ejb-jar.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
version="3.0">
     <assembly-descriptor>
          <security-role>
               <description>
                    Test Role.
               </description>
               <role-name>TestRole</role-name>
          </security-role>
     </assembly-descriptor>
</ejb-jar>
The weblogic-ejb-jar.xml file:
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
     <security-role-assignment>
          <role-name>TestRole</role-name>
          <principal-name>TestUser</principal-name>
     </security-role-assignment>
</weblogic-ejb-jar>I would have thought that the onMessage of the MDB would print "Handling message for user TestUser", but instead it prints "Handling message for user <anonymous>".
It seems as though the @RunAs annotation has no effect. Although I specified the role TestRole (mapped to the user TestUser), the code still seems to be executed by user anonymous.
Am I missing something?
Any help would be much appreciated! I've been looking at this poblem for quite a while now.

Both beans (the MDB on WLS 10 and the session bean on WLS 8.1) use container managed transactions.
For the MDB I do not explicitly set the transaction attributes, so it should default to container managed transactions.
For the stateless session bean I have specified the following in the ejb-jar.xml file:
<ejb-jar>
<display-name>Weblogic8Service</display-name>
<enterprise-beans>
    <session>
      <ejb-name>Weblogic8Service</ejb-name>
      <home>be.cegeka.rszv.test.session.Weblogic8ServiceRemoteHome</home>
      <remote>be.cegeka.rszv.test.session.Weblogic8ServiceRemote</remote>
      <ejb-class>be.cegeka.rszv.test.session.Weblogic8ServiceBean</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>
    </session>
</enterprise-beans>
<assembly-descriptor>
    <container-transaction>
      <method>
        <ejb-name>Weblogic8Service</ejb-name>
        <method-name>*</method-name>
      </method>
      <trans-attribute>Required</trans-attribute>
    </container-transaction>
</assembly-descriptor>
</ejb-jar>So as far as I understand it the transaction starts at the MDB (upon receival of a message). The transaction for the remote call to the stateless session bean (in the onMessage() of the MDB) is included in the transaction of the MDB and gets committed when the onMessage() method finishes and the transaction of the MDB itself gets committed.
Correct me if I'm wrong here.

Error during deployment of Message Driven Bean

Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          I am getting some error (or perhaps warning) during deployment of Message
          Driven Bean. Any one seen this before?
          This error only comes on a machine with Dual Network card.
          Thanks.
          ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
          <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
          enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
          Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
          is of a non-final version of the appropriate specification. It is subject to
          change in future releases once the specification becomes finalized. This may
          cause application code developed for BEA WebLogic Server 6.1 that uses the
          new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          supported in future releases of BEA WebLogic Server.>
          ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          container will automatically attempt to re-establish the connection with the
          JMS server. 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:
          Unable to create a JNDI InitialContext to lookup the JMS destination. The
          error was:
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          nested exception is:
          java.net.ConnectException: Connection refused: connect; No available router
          to destination
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:307)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:211)
          at
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          ory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          rivenBeanInfoImpl.java:641)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          nPoller.java:474)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          .java:418)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          nectionPoller.java:286)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          foImpl.java:511)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:170)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:360)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          Target.java:285)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          eploymentTarget.java:239)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          entTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy34.updateDeployments(Unknown Source)
          at
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          ServerMBean_CachingStub.java:2977)
          at
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          icationManager.java:372)
          at
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          r.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy49.start(Unknown Source)
          at
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010009> <EJB Deployed EJB with JNDI name
          ASYNCMessageDrivenBean.>


Hi Tom
          Yes we do have an URL provided in the descriptor. It's
          t3://jms.server.net:7001.
          and the jms.server.net is resolved via a hosts file in Win2K
          eg,
          192.168.100.200 jms.server.net
          You are right in saying that the loopback in a dual-net card is a problem.
          But our solution
          above solves the issue as long as your host file does not use 127.0.0.1 as
          the IP.
          We need the URL b/c depending on our client's deployment , the JMS Server
          may be remote or may be local.
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Hi x,
          >
          > Something to do with the loopback and dual-network cards is
          > messin' with WLS' mind. I do not know what the problem is,
          > but I can guess:
          >
          > You have specified an URL in the MDB descriptor when there
          > is no need for one. If t3://127.0.0.1:7001 is in the same
          > cluster the MDB is running in (I suspect this URL is
          > actually the same WL server), then don't specify the URL.
          > This URL is only useful for connecting an MDB to a JMS
          > server that is outside local server and outside the cluster.
          > The URL may be working on single-network card systems
          > as perhaps then WL has enough info to guess that you
          > actually mean the local WL server, and simply converts
          > the context to a local context.
          >
          > Note that the URL option in the MDB descriptor is actually
          > a WebLogic extension of J2EE.
          >
          > Tom
          >
          >
          >
          > x wrote:
          > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          > >
          > > I am getting some error (or perhaps warning) during deployment of
          Message
          > > Driven Bean. Any one seen this before?
          > > This error only comes on a machine with Dual Network card.
          > >
          > > Thanks.
          > >
          > >
          > >
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
          features
          > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
          1.2,
          > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
          6.1
          > > is of a non-final version of the appropriate specification. It is
          subject to
          > > change in future releases once the specification becomes finalized. This
          may
          > > cause application code developed for BEA WebLogic Server 6.1 that uses
          the
          > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          > > supported in future releases of BEA WebLogic Server.>
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          > > container will automatically attempt to re-establish the connection with
          the
          > > JMS server. 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:
          > > Unable to create a JNDI InitialContext to lookup the JMS destination.
          The
          > > error was:
          > > javax.naming.CommunicationException. Root exception is
          > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          > > nested exception is:
          > > java.net.ConnectException: Connection refused: connect; No available
          router
          > > to destination
          > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > at
          javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          > > at
          javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > > at javax.naming.InitialContext.init(InitialContext.java:217)
          > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          > > rivenBeanInfoImpl.java:641)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          > > nPoller.java:474)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          > > .java:418)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          > > nectionPoller.java:286)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          > > foImpl.java:511)
          > > at
          weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > at weblogic.j2ee.Application.addComponent(Application.java:170)
          > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > arget.java:360)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          > > Target.java:285)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          > > eploymentTarget.java:239)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          > > entTarget.java:199)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy34.updateDeployments(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          > > ServerMBean_CachingStub.java:2977)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          > > icationManager.java:372)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          > > r.java:160)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy49.start(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          > > ApplicationManagerMBean_CachingStub.java:480)
          > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > > at weblogic.management.Admin.finish(Admin.java:644)
          > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > > at weblogic.Server.main(Server.java:35)
          > >
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010009> <EJB Deployed EJB with JNDI name
          > > ASYNCMessageDrivenBean.>
          > >
          > >
          >

Create EJB 3.0 Message Driven Bean on a Oracle JMS (AQ)

Similar Messages

Maybe you are looking for