Fixes are available
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Using a WebSphere MQ messaging provider activation specification which specifies a WebSphere MQ Queue Sharing Group (QSG) name in the "Queue manager" field with a WebSphere MQ messaging provider queue which also specifies a QSG name in the "Queue manager or Queue sharing group name" field will break with the following exception: javax.jms.JMSException: CWWMQ0048E: An internal error has occurred. The mismatching values are M4P0 and the queue manager portion of queue://QSG2/PriceChangeOneWayJMSServiceQueue? putAsyncAllowed=1&readAheadAllowed=1. at com.ibm.ws.wmqra.helper.WASRuntimeHelper. getCraMessageReferenceHandler(WASRuntimeHelper.java:484) at com.ibm.mq.connector.inbound.MessageEndpointDeployment. createConnectionConsumer(MessageEndpointDeployment.java:369) at com.ibm.mq.connector.inbound.MessageEndpointDeployment. start(MessageEndpointDeployment.java:232) at com.ibm.mq.connector.inbound.MessageEndpointDeployment. <init>(MessageEndpointDeployment.java:204) at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation (ResourceAdapterImpl.java:452) at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.activateEndpoint (ActivationSpecWrapperImpl.java:331) at com.ibm.ejs.j2c.RAWrapperImpl.activateEndpoint (RAWrapperImpl.java:1077) at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint (RALifeCycleManagerImpl.java:1676) This problem can be worked around by using a queue which doesn't specify a QSG name in the "Queue manager or Queue sharing group name" field.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 7.0* **************************************************************** * PROBLEM DESCRIPTION: CWWMQ0048E error for a WebSphere MQ * * message-driven bean consuming from a * * JMS Queue with a queue-sharing group * * (QSG) specified * **************************************************************** * RECOMMENDATION: * **************************************************************** The CWWMQ0048E error occurs during startup of the message-driven bean application, after it has established a connection to a queue manager in the QSG. The error occurs because a comparison is performed between the queue manager name of the member of the QSG to which the connection is established, and the the QSG name specified in the JMS Queue definition. The comparison is performed as part of constructing the lookup details to determine the WLM classification to use for the message-driven bean. The code incorrect assumes the resolved queue manager name from the connection, and the configured queue manager name (QSG name) from the JMS Queue are always the same.
Problem conclusion
The fix for this APAR removes the invalid comparison, and causes WLM classification to use the resolved queue manager name from the connection without looking at the queue manager name configured on the JMS Queue. WLM classification is always performed using the resolved queue manager name, and is never performed using the queue sharing group name. Regardless of whether the fix for this APAR is applied, is it not possible to perform WLM classification using a queue sharing group name. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. Please 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
PK98388
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-12
Closed date
2009-12-16
Last modified date
2009-12-16
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
PLAT MSG COM
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
Document Information
Modified date:
25 October 2021