MDB not listening to JMS Queue

We are using OC4J 10.1.2 We are using JMS for queueing, the Queueing application sucessfully displays the JMS message id, but MDB is NOT listening to the JMS for some reason. We have verified the deployment config files etc. Can amy one help

1 - It doesn't appear that targets were set for any of the administered WL objects. In WL, most administered objects must have a configured target so that WL knows which servers to run them on.
2 - There's no need to specify a URL or initial-context-factory in the MDB. In your case, you're referencing JNDI objects on the MDB's local cluster (which, in turn, map to foreign references).
3 - Note that URL and connection-factory have been re-specified in the foreign JMS server properties, and there 's a mix of delimiters ";" and " ". Normally, no JNDI props are needed except, depending on the use case, for security credentials.

Similar Messages

Urgent : MDB stops listening to the queues after some time !!!

Hi,
I am using OJMS with OC4J 10.1.2 and db 9.2.0.5. I have a web application which send messages into the queue very frequently.
But the problem is the MDBs stop listening to the queues after some time (1-2 days) and no more messages will be dequeued from that point.
All these messages will move to the exception queue after their expiry.
But the dequeing agains resumes after restarting the OC4J !.
I guess, at some point mdbs are either becoming busy (locked ) or some exception occured while dequeing, hence they stop listening to the queues.
Please throw some light on this issue as it is very crucial in my project.
Regards
Prashanth

I've noticed this lately as well, with my iPhone 4. I couldn't confidently pin it directly on any particular iOS update, but my iPhone used to automatically connect up via Bluetooth with my Prius's handsfree feature, and now it doesn't. I work with a CE-based device at my job, with Bluetooth capability, and I used to test out that feature by having it discover my iPhone. This no longer works either.
What I have found (not really a solution, but it does work and may be a clue for Apple) is that if I simply go to the Settings app then the General -> Bluetooth screen and let it sit there, it will pair right up with my car within a few seconds. Bluetooth is always on, and always says "Now Discoverable" at the bottom of the settings screen.

How to stop and start MDBs to listen for JMS messages

Hello! This might be more of an architecture question rather than a technical questing, but I post it here, in the lack of a better place...
For several years I have been using Webster and Webster MQ to send messages back and forth to clients. The architecture for the middleware platform has been designed around the functionality of ListenerPorts. Listenerports is a Webster functionality that let you "stop" and start to listen to JMS messages for a given MDB either by admin console, or by JMX.
The arhitecture we used was something like this :
1.Client sends a persistent message to a queue. (order)
2. An MDB pics up the order message, calls a SessionBean that "fronts" the IIOP back end system.
This is quite "out of the box" architecture, but we used the Listenerports to solve a stability problem for our back end system.
The backEnd system was quite unstable, so the EJB threw an exception (typically because of timeout or connection refused) back to the MDB.
The Listenerport was "defined" to handle 3 errors before stopping, so the MDB resent the message twice before the listenerport automatically stopped. The nice thing about this feature was that the client could continue to send orders, and was not bothered when the back end system was down.
When the backEnd system was up and running, we could start the listenerport and it was all back to normal state. We even had a start script that checked the state of the listenerport every 30 minute, and started it automatically if it was stopped, making the admin task of starting the MDB unnecessary..
Now.. Why am I telling this story..
I would like to know how this could be done using "clean" J2EE technologies..That is..Not using any technology that is not portable..
I`m playing with glassfish at home, and it struck me that there is nothing in the J2EE spec that defines the functionality described above ? Am i missing something ?
I Do not want to stop My application because the back end system is down? That is the only way (i know of) that i can "stop" to listen for messages..
I can put all the messages on an error queue when the backbend system is down, but that would lead to more code just to handle the error messages. Maybe the easiest way to solve this is to "move" (programmatically) all messages from the error queue over to the "standard" queue every XX minute, but somehow that sounds "wrong"
Can anyone give me some advice to how this problem situation should be solved ? I`m interested in the solution both from an architectural perspective and from a more technical perspective..
Best regards
Hans-Jacob Melby

Breakpoints, whether normal or conditional, are just meant for debugging of your code. I had the sense from your question that the pausing you want to do is a part of normal operation of your code. I would NOT recommend using a breakpoint for that situation. It would bring up the block diagram showing the breakpoint when it occurs. A user besides the programmer would not know what to do in that case.
Yes, both the inner and outer loops would have shift registers.
Putting a case structure with a small while loop inside the "Pausing Case" is doable. It just depends on what you are doing or waiting for while the program operation is "paused".

Single MDB on a clustered JMS queues(2)

I have 2 JMS servers in a cluster and each server has a JMS queue, which forms the distributed destination. Now I need a MDB to listen on both these queues. Is it possible?
Thanks
-Ankur

Yes - thats the usual purpose of distributed queues, to allow consumers to consume from the distributed queue (wherever its hosted).
Though distributed destinations are JMS provider specific so do check your providers documentation on using distributed queues. In some providers, like ActiveMQ, distributed queues look and act just like regular queues so they just work from inside a JMS client or MDB.
James
http://logicblaze.com/

Proxy Service listening a JMS Queue

HI all,
I have a simple question.
I have an web application that write a message into a JMS Queue.
I wanna know if when a message arrives into a JMSQueue an ESB proxy can listen this queue, get the message and afterwards process it.
Thanks and Regards!

Hi,
In ALSB 2.6 its very much possible. Create a proxy Service (Any XML Service) configure your endpoint to the queue. provide correct Url, Connection factory JNDI and queue JNDI to the endpoint.
Hope this helps you.
~Anup

Mbean that listen for jms queue messages

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Hi to all,
          I must use a Jmx notification listener architecture to trap when a new message arrives (i must also handle the message content) in a weblogic jms queue.
          Do you know which mbean could help me to observe the new ariving message?
          In the javadocs i cant' find any useful mbean to do that..
          Thanks

Process not writing to JMS queue with non-xa data source

I have a process reading from a JMS-AQ with non XA, but it does not seem to be performing a commit and writing to the queue. If I use XA all the way ut works, but I don't get the desired error handling which I have built. Anything obvious I am missing? 11.1.1.5 SOA

Hi,
Under Weblogic JDBC Datasources select the datasource and then select Transaction tab there you can find Use XA datasource interface.
and In DB adapter ... go to Configuration Tab ---Outbound Connection Pool--- Unhide the pool group -Select JNDI name ( e.g eis/DB/local ) ---enter the JDBC datasource created earlier in weblogic JDBC datasource against xADataSourceName..
Now Click on Transaction tab & select Transaction Support: as XA Transaction .
Regards,
Abhinav Gupta

MDBs in 9.1 continue to consume JMS queues even after being deleted

<b>We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.</b>
          <b>First, we had an issue where our MDBs were causing the following exception:</b>
          <i>####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
          java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
               at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
               at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
               at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
               at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
               at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
               at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
               at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
               at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
               at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
               at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
               at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
               at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
               at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
               at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
               at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
               at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
               at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
               at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
               at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
               at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
               at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
               at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
               at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
               at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
          >
          ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.></i>
          <b>
          Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:</b>
          <i>####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
          ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
          ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
          ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.></i>
          <b>
          This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
          Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
          I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
          I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
          Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
          Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.</b>

I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
          Tom

Configuring a BEA WebLogic 7.0 Server and MDB to Listen on an Oracle Queue

I am tasked with configuring a BEA WebLogic 7.0 SP1 Server, and deploying an MDB to listen to a queue created in Oracle Advanced Queuing. Has anyone had any experience in making this work? And if so, could you send me some sample code/XML that illustrates such?
Thanks!

See my reply at Deploying MDB on BEA WebLogic 7.0 to listen to Oracle AQ

Web service which listens/replies over JMS Queues/Topics - HOW?

Hi all,
I need help - I have to implement the following Web Service for Weblogic 8.1:
- Simple Helloworld operation
- The Web service should listen on a Queue(or Topic) - say Queue1
- The response of the service should be put in another queue - predefined - say Queue2(or taken as propetry of the request "ReplyTO")
I looked for such an implementation in the available examples and forum topics, but without luck.
Please, give an example or a guide how to implement such a service if possible!
Thanks,
Ivo

Hi,
I have a work around to this problem please see if it suits you or you might already be knowing it.
Workaround is
1. Create a Simple Webservice as needed which puts a message in a Queue.
2. Create an MDB which listens to you Queue / Topic and call the created webserivce in the onMessage function of the MDB.
Vivek

Issue with lock file in Oracle 10g app server - MDB not running

Hi,
I have Oracle 10g & MQ 6 on my laptop. I generated JNDI bindings for app server-MQ by giving ip address of my machine first. Then i changed it to "localhost" & generated new set of .bindings file.
With this new set i am able to send messages from my program to a queue. I also have an MDB which should listen to the same queue.
However now my mdb is not listening to the queue & i suspect it is due to host address change, - because each time i start the server, i see a lock file created "OracleASRouter_store.lock" - under j2ee\home\persistance. And below is the content of the same -
"O10.1.4.245:/C:/Program Files/Oracle/oc4j_extended_101330/j2ee/home/persistence/"
As per few suggestions on this site, I deleted this file & restated app server, deleted whole content of persistance folder, restarted app server. But each time i see this file created and also see the ip address in log.xml under j2ee\home\log\oc4j
Error message in this log.xml file is
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2007-09-19T11:22:35.265-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>j2ee</COMPONENT_ID>
<MSG_ID>J2EE EJB-02009</MSG_ID>
<MSG_TYPE TYPE="WARNING"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>IFLEXNY-EXT99</HOST_ID>
<HOST_NWADDR>10.1.4.245</HOST_NWADDR>
<MODULE_ID>ejb.runtime</MODULE_ID>
<THREAD_ID>10</THREAD_ID>
<USER_ID>chetanmi</USER_ID>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>10.1.4.245:65858:1190215355296:0</UNIQUE_ID><SEQ>0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>[STGMQ:STGMQEJB:TestMDB] Unexpected exception by JMS provider: javax.jms.MessageEOFException: initializeConnection.</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[javax.jms.MessageEOFException: initializeConnection
     at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1075)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1155)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:154)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:110)
     at com.evermind.server.jms.TCPJMSRemoteServer.<init>(TCPJMSRemoteServer.java:68)
     at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:122)
     at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:70)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.unprivileged_createQueueConnection(EvermindQueueConnectionFactory.java:101)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.access$000(EvermindQueueConnectionFactory.java:44)
     at com.evermind.server.jms.EvermindQueueConnectionFactory$1.execute(EvermindQueueConnectionFactory.java:81)
     at com.evermind.server.jms.InContainerProxy.doSecureOp(InContainerProxy.java:157)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:78)
     at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(EvermindQueueConnectionFactory.java:69)
     at com.evermind.server.ejb.MessageDrivenConsumer.createNonXAResources(MessageDrivenConsumer.java:567)
     at com.evermind.server.ejb.MessageDrivenConsumer.initializeJMSResources(MessageDrivenConsumer.java:491)
     at com.evermind.server.ejb.MessageDrivenConsumer.processMessages(MessageDrivenConsumer.java:208)
     at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:169)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.EOFException
     at java.io.DataInputStream.readInt(DataInputStream.java:358)
     at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:678)
     at com.evermind.server.jms.JMSRemoteServer.readProtocol(JMSRemoteServer.java:696)
     at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:134)
     ... 16 more
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2007-09-19T11:22:35.312-04:00</TSTZ_ORIGINATING>
<COMPONENT_ID>j2ee</COMPONENT_ID>
<MSG_ID>J2EE EJB-02014</MSG_ID>
<MSG_TYPE TYPE="WARNING"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>IFLEXNY-EXT99</HOST_ID>
<HOST_NWADDR>10.1.4.245</HOST_NWADDR>
<MODULE_ID>ejb.runtime</MODULE_ID>
<THREAD_ID>10</THREAD_ID>
<USER_ID>chetanmi</USER_ID>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>10.1.4.245:65858:1190215355296:0</UNIQUE_ID><SEQ>0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>[STGMQ:STGMQEJB:TestMDB] All message consumer threads have terminated due to provider errors, stopping MDB.</MSG_TEXT>
</PAYLOAD>
</MESSAGE>
And my MDB is NOT WORKING. Please let me know how to deal with this.
Your suggestions would be much appreciated.
Regard,
Chetan

Line # 127 is creating a new application object using ApplicationFactory.
ApplicationFactory aFactory =
(ApplicationFactory) FactoryFinder.getFactory(
FactoryFinder.APPLICATION_FACTORY);
application = aFactory.getApplication();
The only way that can throw a null pointer is when aFactory is NULL. I really doubt this case because, the same thing is doen in init() of FacesServlet. If it had failed there, the exception should have occured during server startup.
This leaves me more and more confused....I am desperate for some help now :((
Ramesh

How to configure JMS queue on OC4J server. Development in JDeveloper 10G

Hi there,
I have to configure a JMS for an Asynchronous process in my Application which will be running in Oracle 10G Application Server. Development Environment is Oracle JDeveloper 10G.
I am facing a problem on how to configure JMS queue.
Steps Followed are:
in the <JDevloperHome>/j2ee/home/config
1. Made the new queue and connection factory's JMS entry in jms.xml.
2. Specifed the queue in oc4j-connectors.xml.
3. played around with application.xml
and tried all combinations, but the message producer always failed to lookup the queue.
Need help on the steps to follow so that the producer can post the message in the queue.
Also please help how to configure the MDB to listen to the queue.
Thanx and Regards
Subham

If you were dealing with Oracle 10g app server as opposed to standalone, I might be better able to help you.
One thing though, when you are configuring your MDB in the orion-ejb-jar.xml file, do not forget to specify attribute listener-threads, otherwise no matter how many beans you have in your MDB pool, only one bean will be listening to the queue. Many listener-threads equal to max number of beans in pool.

MDB topic listener and concurrent processing

Hello to everybody.
I ve prototyped simple db publisher ,which publishes changed data from database to JMS topic. Then I have my MDB which listens on JMS topic.
I setup and implemented all correctly and it worked. There was 1 consumer = 1 mdb instance. Then I tried to do load testing , So I triggered 8000 changes from database. The db adapter did the job and published the 8000 messages on the JMS topic in a while. To mimic processing in MDB I put the sleep(10seconds) in MDB.
MDB topic processing seems to me as not concurrent one. Why? I observed 10 message decrease with 5-10 seconds.
What I expected was: concurrent processing of 8000 JMS messages by 1 MDB (so MDB is poolable component isnt it?).
So for 500 instances of topic MDB and 8000 messages on the JMS topic, I expected at least 8000/500 X 10 = 160 seconds to process message load.
I am using WLS 816.
Can You give me some hits.
Thanks
Roman

I did the same test on Weblogic 10 and it worked as expected. MDB durable subscriber consumed 8000 messages (each msg processing had 10 secs sleep inside.) within 2 minutes. So it is ok.
But why it did not worked on WLS 8.1? Is this a bug ?

Getting events into WLI from External JMS Queue

Hi,
I can't figure out how to get an event into WLI from an external JMS queue.
I can send an XML message to an external queue but can't figure out how to get
a message from an external queue into WLI. I have created the MDB using the generator
program provided and have deployed. How does this MDB now send these messages
into WLI?
I have also posted this same question in weblogic.interest.jms newsgroup.
-- Bill

Hi Bill.
Actually this is really simple. Here are the steps:
Connect your MDB to the external JMS queue by modifying the weblogic-ejb-jar.xml
The MDB onMessage(Message m) method will receive a message from the external JMS
queue. It will then use JNDI to bind to the EventQueue of WLI and submit the event
as XML into that queue.
Obvously the onMessage() operation must be transacted using container managed
transactions so the scope will spawn both de-queuing from the external JMS queue
and enqueing into the WLI Evnet Queue.
"Bill Ozeroff" <[email protected]> wrote:
>
Hi,
I can't figure out how to get an event into WLI from an external JMS
queue.
I can send an XML message to an external queue but can't figure out how
to get
a message from an external queue into WLI. I have created the MDB using
the generator
program provided and have deployed. How does this MDB now send these
messages
into WLI?
I have also posted this same question in weblogic.interest.jms newsgroup.
-- Bill

Stop MDB from listening to a JMS queue

Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

If you can tune the number of messages that should be sent to the MDB to 0, that would
temporarily stop the MDB from consuming messages. Thsi is the "Messages maximum"
parameter on ur connectionfactory. WL6 doesnt support changing this value to 0 but there
were some newsgroup discussions last year that it might be supported in a future
release. Maybe its fixed in 8?
Eric Poupaert wrote:
Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

MDB not listening to JMS Queue

Similar Messages

Maybe you are looking for