|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
WMQ v7.0.1.0 |
« View previous topic :: View next topic » |
Author |
Message
|
manojsu |
Posted: Wed Nov 10, 2010 6:03 am Post subject: WMQ v7.0.1.0 |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi Guys,
We have upgraded WMQ from 6.0.2.1 to 7.0.1.0, with Adapter for JDBC v2.6.9.
After the upgrade was done an FDC was generated and the JDBC adapter kept appendig the logs with the error below.
Abend -
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu October 14 2010 10:41:28 GMT |
| UTC Time :- 1287052888.020820 |
| UTC Time Offset :- 0 (GMT) |
| Host Name :- sfsdevp |
| Operating System :- AIX 5.3 |
| PIDS :- 5724H7221 |
| LVLS :- 7.0.1.0 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- JM005008 |
| Application Name :- MQM |
| Component :- Java_com_ibm_mq_jmqi_local_internal_base |
| SCCS Info :- com.ibm.mq.jmqi.local/src/native/trace.c, 1.20 |
| Line Number :- 554 |
| Build Date :- Aug 13 2009 |
| CMVC level :- p000-L090813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 9000 (esbadmin) |
| Real UserID :- 9000 (esbadmin) |
| Program Name :- java |
| Addressing mode :- 32-bit |
| Process :- 356840 |
| Thread :- 5 |
| UserApp :- TRUE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- OK |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 1 |
| Comment1 :- ExceptionOccured |
| |
Adapter Logs
[Time: 2010/11/10 10:48:27.456] [System: Server] [Thread: QL.ACES.ADMIN.INJmsThreadPool.thread5 (#1744432739)] [Mesg: Could not find worker for CxCommon.Messaging.jms.Receiver$ThreadCallBackImp@6decee6a.]
[Time: 2010/11/10 10:48:27.464] [System: ConnectorAgent] [SS: ACES_JDBC_PRDConnector] [Thread: QL.ACES.ADMIN.INJmsThreadPool.thread4 (#1744678499)] [Type: Error] [MsgID: 9061] [Mesg: Caught JMS error. Reason: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2002: Failed to get a message from destination 'QL.ACES.ADMIN.IN'. WebSphere MQ classes for JMS attempted to perform an MQGET; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error..]
[Time: 2010/11/10 10:48:27.464] [System: ConnectorAgent] [SS: ACES_JDBC_PRDConnector] [Thread: QL.ACES.ADMIN.INJmsThreadPool.thread4 (#1744678499)] [Type: Error] [MsgID: 9062] [Mesg: JMS Exception Error code: JMSWMQ2002. Exception message: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2195' ('MQRC_UNEXPECTED_ERROR')..]
[Time: 2010/11/10 10:48:27.466] [System: Server] [Thread: QL.ACES.ADMIN.INJmsThreadPool.thread4 (#1744678499)] [Mesg: java.lang.NullPointerException
at CxCommon.Messaging.jms.Receiver$ThreadCallBackImp.reReceive(Receiver.java:240)
at CxCommon.Messaging.jms.Receiver$ThreadCallBackImp.callback(Receiver.java:345)
at CxCommon.ThreadingServices.ThreadPoolThread.run(ThreadPoolThread.java:175)
]
mqjms.log
10/11/2010 11:50:21 [QL.JDBC.BKR.ACE.01JmsThreadPool.thread1] com.ibm.msg.client.wmq.internal.WMQConnection
Exception ignored as no exception listener is registered: '
Message : com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A problem with this connection has occurred. An error has occurred with the WebSphere MQ JMS connection. Use the linked exception to determine the cause of this error.
Class : class com.ibm.msg.client.jms.DetailedJMSException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:608)
: com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:236)
: com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:117)
: com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQConsumerShadow.java:1198)
: com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receiveInternal(WMQSyncConsumerShadow.java:233)
: com.ibm.msg.client.wmq.internal.WMQConsumerShadow.receive(WMQConsumerShadow.java:922)
: com.ibm.msg.client.wmq.internal.WMQMessageConsumer.receive(WMQMessageConsumer.java:450)
: com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:742)
: com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:423)
: com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:258)
: CxCommon.Messaging.jms.SecurityProxy.ReceiveProxy.receive(ReceiveProxy.java:72)
: CxCommon.Messaging.jms.Receiver$ThreadCallBackImp.callback(Receiver.java:304)
: CxCommon.ThreadingServices.ThreadPoolThread.run(ThreadPoolThread.java:175)
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2195' ('MQRC_UNEXPECTED_ERROR').
Class : class com.ibm.mq.MQException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
: com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:117)
: com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQConsumerShadow.java:1198)
: com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receiveInternal(WMQSyncConsumerShadow.java:233)
: com.ibm.msg.client.wmq.internal.WMQConsumerShadow.receive(WMQConsumerShadow.java:922)
: com.ibm.msg.client.wmq.internal.WMQMessageConsumer.receive(WMQMessageConsumer.java:450)
: com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receiveInboundMessage(JmsMessageConsumerImpl.java:742)
: com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl.receive(JmsMessageConsumerImpl.java:423)
: com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:258)
: CxCommon.Messaging.jms.SecurityProxy.ReceiveProxy.receive(ReceiveProxy.java:72)
: CxCommon.Messaging.jms.Receiver$ThreadCallBackImp.callback(Receiver.java:304)
: CxCommon.ThreadingServices.ThreadPoolThread.run(ThreadPoolThread.java:175)
'
EXPLANATION:
An attempt was made to deliver an exception to the connections exception listener but a listener has not been registered
Any idea or has anyone encountered the same.
Thanks |
|
Back to top |
|
 |
zpat |
Posted: Wed Nov 10, 2010 7:48 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You could start by installing Fixpack 7.0.1.3 or use the base version which is now shipped at 7.0.1.3. |
|
Back to top |
|
 |
manojsu |
Posted: Wed Nov 10, 2010 7:57 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
thank you, that is the option i am considering, but would be good to know the reason of error before proceeding towards it. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Nov 10, 2010 1:28 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
manojsu wrote: |
thank you, that is the option i am considering, but would be good to know the reason of error before proceeding towards it. |
For all you know it could be a bug that is fixed at level 7.0.1.3.
Consider anything @ V7.0.1 before 7.0.1.3 to have been retired from circulation.  _________________ MQ & Broker admin |
|
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
|
|
|
|