APAR status
Closed as duplicate of another APAR.
Error description
A message-driven bean (MDB) running on a WebSphere Application Server 7 is configured to use the WebSphere MQ messaging provider. While starting a Java Message Service (JMS) application, the WebSphere Application Server startup hangs during the MDB activation if the queue has multiple messages. . The SystemOut.log shows some warnings like this: . ?timestamp? 00000003 ThreadMonitor W WSVR0605W: Thread "WMQJCAResourceAdapter : 0" (00000026) has been active for x milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:167) at com.ibm.ejs.container.MessageEndpointFactoryImpl. createEndpoint(MessageEndpointFactoryImpl.java:497) at com.ibm.mq.connector.inbound.WorkImpl.run (WorkImpl.java:192)
Local fix
As a workaround, delete messages from the WMQ queue and restart the WAS application.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere Application Server V7 WebSphere MQ messaging provider who use Activation Specifications. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: This issue is caused when an application with multiple MDBs is started where the associated activation specification's source queue contained a number of messages. The issue is described further in IZ68236. The fix described is to set the connectionConcurrency property on the Resource Adapter to 1. Further to IZ68236, the property must be set at the cell scope in order to be applied correctly. Diagnosis of this issue is complicated by the application server classes tracing out the value from the server scope. This APAR has been closed as a duplicate of IZ68236.
Problem conclusion
Temporary fix
Comments
This APAR is a duplicate of IZ68236
APAR Information
APAR number
IZ90895
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED DUB
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-12-14
Closed date
2011-01-27
Last modified date
2011-11-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]
Document Information
Modified date:
21 April 2021