MQJMS1016: an internal error has occurred

[nozicka]

Hello!

We are using WebSphere Appl Server 5.1 with FixPack 1 in Production and FixPack 3 on the test system on a Linux390 System. We use message driven beans (MDBs) and the embedded messaging system. We run a kind of batch to start our transactions. The logic behind does always the same for each MDB. Starting the batch works and one message after each other is processed. But from time to time (not deterministic) we get the exception listed below on both systems (usually we run between 40 and 200 transactions for each batch; there is no run without this error happening at least 2 or 3 times per batch). The system recovers after 60 seconds and continues to process the MDBs. Anyhow, the question is what can be the reason? Any ideas?

[4/23/04 17:25:52:462 GMT] 510e7962 JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB AsyncOCR , JMSDestination jms/OCRQueue : javax.jms.JMSExc
eption: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: {0}
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java(Inlined Compiled Code))
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java(Compiled Code))
at java.lang.Thread.run(Thread.java(Compiled Code))
---- Begin backtrace for Nested Throwables
java.lang.NullPointerException
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java(Compiled Code))
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java(Compiled Code))
at java.lang.Thread.run(Thread.java(Compiled Code))

[4/23/04 17:25:52:464 GMT] 510e7962 JMSExceptionL E WMSG0057E: Error on JMSConnection for MDB AsyncOCR , JMSDestination jms/OCRQueue , JMS Linked Except
ion : java.lang.NullPointerException
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java(Compiled Code))
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java(Compiled Code))
at java.lang.Thread.run(Thread.java(Compiled Code))

[4/23/04 17:25:52:466 GMT] 510e7962 MDBListenerIm I WMSG0043I: MDB Listener OCRPort stopped for JMSDestination jms/OCRQueue
[4/23/04 17:25:52:825 GMT] 510e7962 MDBListenerIm I WMSG0058I: Listener Port OCRPort will attempt to restart in 60 seconds
[4/23/04 17:25:52:826 GMT] 510e7962 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for re
source jms/ZSDBJMSConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please cont
act your system administrator. Detail: {0}
[4/23/04 17:26:52:859 GMT] 4fd7961 MDBListenerIm I WMSG0042I: MDB Listener OCRPort started successfully for JMSDestination jms/OCRQueue

[jackgodau]

Have a look at:

PQ76202: Container seems unable to successfully rollback a transaction

http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=WMSG0018E&uid=swg1PQ76202&loc=en_US&cs=utf-8&lang=en+en

Cheers
Jack...

[kpsunil]

I am getting the same error as soon as I set up a cluster with 2 nodes. I haven't seen this error in a normal single Base server mode.

I do get this message as soon as I start my server. I do not have to run any thing in my application. So, the previous answer suggesting that this is an Application related error can not be true??? Could this be because of an old message sticking around some where that gets re processed every time I restart the server? I do not see any thing in my application logs either. If this is coming form an old message, how do I get rid of it? Or how do I make sure that undelivered messages are retried only 3 times or so?

Using WAS 5.1 SP4, embedded JMS.

Thanks

K P Sunil

[10113171]

I think I have the exact same behaviour, I am running WAS 5.1.2 test environment under WSADIE 5.1:

[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.<init>(Throwable.java:59)
at java.lang.Throwable.<init>(Throwable.java:73)
at javax.jms.JMSException.<init>(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.<init>(Throwable.java:59)
at java.lang.Throwable.<init>(Throwable.java:73)
at java.lang.NullPointerException.<init>(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.<init>(Throwable.java:59)
at java.lang.Throwable.<init>(Throwable.java:73)
at java.lang.NullPointerException.<init>(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)

[Ronald Bower]

I believe this is APAR IC38409. If you'll update the WMQ that you are using
beyond CSD4, the problem should be resolved.

Ron

"10113171" <jlr...@workstar.co.uk> wrote in message
news:113595790.1090878155410.JavaMail.wasadmin@swg3ws006...

[emma...@pirsch.org]

I'm experiencing a similar problem.

We are using WebSphere 5.1.1.8. Is this issue supposed to be solved in this fix pack? Is it resolved in 5.1.1.9?

Unfortunately, we do not have the luxury to install the standalone WebSphere MQ. So we need it to be fixed in the MQ Embedded in WebSphere AS.

We configured our queue connection factory to be not XA. Is enabling XA help solve the problem?

Thank's in advance!