APAR status
Closed as program error.
Error description
When using WebSphere Application Server V5, an intermittent
Message-Driven Bean (MDB) performance slowdown may occur. The
cause of the problem is that one of the listener threads stops
processing messages. The failing listener thread produces the
following error:
javax.jms.JMSException: MQJMS2002: failed to get message from MQ
queue
at
com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnv
ironment
.java(Inlined Compiled Code))
at com.ibm.mq.jms.MQSession.consume(MQSession.java(Compiled
Code))
at com.ibm.mq.jms.MQSession.run(MQSession.java(Compiled Code))
at
com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java(Compi
led
Code))
at
com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessa
ge(Serve
rSession.java(Compiled Code))
at
com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.j
ava(Compiled Code))
...
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2072
at com.ibm.mq.jms.MQSession.consume(MQSession.java(Compiled
Code))
at com.ibm.mq.jms.MQSession.run(MQSession.java(Compiled Code))
at
com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java(Compi
led Code))
...
The problem was identified in the WebSphere transaction manager
code.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: When more than one transaction was *
* packaged for remote transmission, only *
* the 1st transaction was unpackaged at *
* the remote end. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
TrMsg would package up a number of transactions that were
destined for the same remote server, and then periodically
transmit the packaged transactions to the remote server. The
remote server only unpacked the first transaction in the pile.
Problem conclusion
The transaction packaging was an attempt to reduce traffic on
slow networks - it is no longer considered appropriate. The
transaction is now sent immediately to the remote server.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.10 Please refer to the Recommended Updates page
for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&
context=SSEQTP&uid=swg27004980
Temporary fix
ZE Fix Error
PK02160 05/03/08
Comments
APAR information |
APAR number |
PQ97510 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-11-22 |
Closed date |
2005-02-22 |
Last modified date |
2005-05-17 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|