aspose file tools*
The moose likes BEA/Weblogic and the fly likes JMS message is not picked up by the listener Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "JMS message is not picked up by the listener" Watch "JMS message is not picked up by the listener" New topic
Author

JMS message is not picked up by the listener

Elango Valluvan
Greenhorn

Joined: May 02, 2005
Posts: 8
We have created a queue in a cluster. We have an application that listens to a queue. Messages from another application will post message into this queue which is inturn picked up by the listener process.

We posted a message to the queue long back.But it was not picked up by the application. Then, again we sent two more messages. These recent two messages were picked up by the application.

We looked into the queue using QueueBrowse program from weblogic samples. The program "sometimes" shows that the first message (which was not picked up) is still there in the queue. Sometimes, it shows that there is no message in the queue.

Could any of you help me on this?
Have you faced any such scenarios earlier?

Thanks in advance.
Elango
Elango Valluvan
Greenhorn

Joined: May 02, 2005
Posts: 8
I also found in my queue listener's log the following exception stack trace.

weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.jms.client.JMSConnection.jmsPeerGone(JMSConnection.java:908)
at weblogic.jms.dispatcher.DispatcherWrapperState.peerGone(DispatcherWrapperState.java:691)
at weblogic.jms.dispatcher.DispatcherWrapperState.callback(DispatcherWrapperState.java:552)
at weblogic.rjvm.RJVMImpl$HeartbeatMonitorListenerDeliverer.execute(RJVMImpl.java:1412)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


Is this exception related in any way to the above stated issue?
Elango Valluvan
Greenhorn

Joined: May 02, 2005
Posts: 8
We found the cause for this issue. This kind of scenario will happen if the clustered environment (where the queue is created) is not stable.

Thought of sharing the solution for future references.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JMS message is not picked up by the listener