| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MDB falls over on backout with MQJMS1016 |
« View previous topic :: View next topic » |
| Author |
Message
|
| JLRowe |
 Posted: Wed Jul 28, 2004 5:14 am Post subject: MDB falls over on backout with MQJMS1016 |
 |
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
When I get a poison message on the queue, mq raises the following exception:
| Code: |
[26/07/04 22:28:44:687 BST] 77d077d0 JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB UPESReceive , JMSDestination jms/UPES.INBOUNDQUEUE : javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: {0}
at java.lang.Throwable.(Throwable.java:59)
at java.lang.Throwable.(Throwable.java:73)
at javax.jms.JMSException.(JMSException.java:51)
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1583)
at java.lang.Thread.run(Thread.java:802)
---- Begin backtrace for Nested Throwables
java.lang.NullPointerException
at java.lang.Throwable.(Throwable.java:59)
at java.lang.Throwable.(Throwable.java:73)
at java.lang.NullPointerException.(NullPointerException.java:60)
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java:368)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1557)
at java.lang.Thread.run(Thread.java:802)
[26/07/04 22:28:44:718 BST] 77d077d0 JMSExceptionL E WMSG0057E: Error on JMSConnection for MDB UPESReceive , JMSDestination jms/UPES.INBOUNDQUEUE , JMS Linked Exception : java.lang.NullPointerException
at java.lang.Throwable.(Throwable.java:59)
at java.lang.Throwable.(Throwable.java:73)
at java.lang.NullPointerException.(NullPointerException.java:60)
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java:368)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1557)
at java.lang.Thread.run(Thread.java:802) |
The listener restarts successfully after 60 seconds, and it does put the poison messages on the backout queue, but having the exception everytime is kind of irritating.
also described in another forum:
http://www-106.ibm.com/developerworks/forums/dw_thread.jsp?forum=266&thread=47355&cat=9
My configuration is as follows:
WAS 5.1.0.2 test server
WMQ 5.3 CSD7
My input queue has a poison queue defined, backout threshold of 1 and get backout is hardened. The listener port has a maximum retry of 1. My desired behaviour is for all messages to be delivered once and backout to a seperate queue if a rollback occurs.
Has anyone come across this error before? are my settings correct? |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Jul 28, 2004 6:37 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| What version of WMQ are you running (use mqver)? I'll bet that it is WMQ 5.3 CSD4. You are probably encounter APAR IC38409. I believe the latest CSD fixes this and other NullPointerExceptions. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Jul 28, 2004 7:09 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
I'm on CSD07, but you got me thinking.
My MQ_INSTALL_ROOT variable was still pointing to the embedded message provider, I set it to the path of the full MQ install and it now works fine.
Thanks! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
