Hi,
We have been experiencing this problem for sometime. We have this problem of jms messages getting stuck in the queue. When I restart the server the queues are cleared up and they are received. I'm not able to understand the reason why they periodically gets stuck in the queue and do not flow normally unless I have to restart the server.
Here is a error stacktrace from the log file that is thrown, but still I'm not able to identify if this is a code issue or something specific to the environment. Because first whenever I restart the server the queue is cleared up and also the app is running in other environments and the queue do not gets stuck. Can someone provide some light on this it will be highly appreciated.
<Oct 28, 2009 10:33:13 AM EST> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
javax.ejb.TransactionRolle
javax.ejb.TransactionRolle
java.lang.NullPointerExcep
javax.ejb.TransactionRolle
at weblogic.ejb20.internal.EJ
at weblogic.ejb20.internal.Ba
at weblogic.ejb20.internal.Ba
at com.cinr.otf.ejb20.RmProce
at com.cinr.otf.ejb20.MPIPers
at weblogic.ejb20.internal.MD
at weblogic.ejb20.internal.MD
at weblogic.jms.client.JMSSes
at weblogic.jms.client.JMSSes
at weblogic.kernel.ExecuteThr
at weblogic.kernel.ExecuteThr
thank you
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
thanks Sompol for your reply.
But what I do not understand is that the queue stacks up, but when I restart the server they get cleared and they are infact getting consumed and do not expire. So how is that when at the time of message consumption it throws the exception (the exception I had posted earlier), but they get consumed when I restart the server. Remember the queues are all consumed and they do not get expired.
- thank you
For example, someone restart database which datasource in weblogic connecting with; and when database is up and running, weblogic cannot resume its connection. And the is business logic in Mdb need to access to database, so it throws exception.
After restart all db connection is refresh and working again.
Actually, my scenario is happened on particular db and some jdbc driver. Just an example.
Hope this help,
Sompol
Business Accounts
Answer for Membership
by: sompol_kiatkamolchaiPosted on 2009-10-28 at 22:53:32ID: 25690980
Hi swapna84,
It would be possible that there is an exception while MDB consumes and processes the JMS message from queue. When exception occur the message will return back to jms queue. This will happen in looping until the jms message expired.
You can configure to avoid looping by setting redelivery limit to 3 times. The default of this setting is -1 which means unlimited try.
Here is a definition of Redelivery Limit parameter.
"The number of redelivery tries a message can have before it is moved to the error destination. This setting overrides any redelivery limit set by the message sender. If the redelivery limit is configured, but no error destination is configured, then persistent and non-persistent messages are simply dropped (deleted) when they reach their redelivery limit"
Hope this help,
Sompol