PK74661: INCORRECT GENERATION OF ClassNotFoundException FFDCs from MDBListenerManagerImpl.initializeMQJMSConnectionPooling

Fixes are available

APAR status

Closed as program error.

Error description

When starting an application server in Embedded WebSphere
Application Server V6.1, the following FFDC report is seen:

Exception = java.lang.ClassNotFoundException
Source = com.ibm.ejs.jms.listener.MDBListenerManagerImpl.
initializeMQJMSConnectionPooling
probeid = 705
Stack Dump = java.lang.ClassNotFoundException:
com.ibm.mq.MQSimpleConnectionManager
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:130)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.
initializeMQJMSConnectionPooling(MDBListenerManagerImpl.java:925
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startManager
(MDBListenerManagerImpl.java:237)
at com.ibm.ws.runtime.component.MessageListenerImpl.
start(MessageListenerImpl.java:160)
at com.ibm.ws.runtime.component.ContainerImpl.
startComponents(ContainerImpl.java:977)
...
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)

The FFDC report can safely be ignored.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of Embedded WebSphere Application     *
*                  Server V6.1                                 *
****************************************************************
* PROBLEM DESCRIPTION: An FFDC report is incorrectly           *
*                      produced because Embedded WebSphere     *
*                      Application Server V6.1 does not        *
*                      contain the WebSphere MQ JMS client.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The FFDC report is logging that the WebSphere MQ JMS client
classes are not available.
However, the code is aware that the WebSphere MQ JMS client
is unavailable at this point during server startup, and should
avoid attempting to access the WebSphere MQ JMS client and
logging the FFDC report.

Problem conclusion

The FFDC report is no longer produced by an application server
that is unable to locate WebSphere MQ JMS client classes.

A WMSG1605E message continues to be logged to the JVM logs of
the application server.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.3.
Refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK74661
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-29
Closed date
2008-12-01
Last modified date
2008-12-01

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSERVIC FEATU
Fixed component ID
5724J0850

Applicable component levels

R610 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK74661: INCORRECT GENERATION OF ClassNotFoundException FFDCs from MDBListenerManagerImpl.initializeMQJMSConnectionPooling

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R610 PSY

Document Information

Share your feedback

Need support?