APAR status
Closed as program error.
Error description
A topic/connection factory connection is made for a JMS client connection from WebSphere Application Server (WAS) to an MQ queue manager. Errors include: ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option. Alternatively check that the Database or MessageProvider is available. ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource <connection factory name>. The exception is: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0026: Failed to subscribe to topic '<topicname>' using MQSUB. There may have been a problem creating the subscription due to it being used by another message consumer. Make sure any message consumers using this subscription are closed before trying to create a new subscription under the same name. Please see the linked exception for more information.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2195' ('MQRC_UNEXPECTED_ERROR'). The FDC information includes: Probe Id :- AT118004 Component :- atmRegisterSyncExits Job Description :- QMQM/AMQZLAA0 Submitted By :- jobnum/QMQM/AMQZXMA0 Major Errorcode :- arcE_XAER_PROTO Minor Errorcode :- OK Probe Type :- INCORROUT Probe Severity :- 2 Probe Description :- AMQ6125: internal MQ error Corresponding errors in the amqerr01.log are: - AMQ6125: An internal WebSphere MQ error has occurred. EXPLANATION: Cause . . . . . : An internal error has occurred with identifier X'20807594'... - AMQ6184: An internal WebSphere MQ error has occurred. - AMQ6118: An internal WebSphere MQ error has occurred (X'20807594') Additional Symptom(s) Search Keyword(s): WSAS pubsub publish subscribe
Local fix
Temporarily set the channel so that it does not used shared conversations: ALTER CHANNEL(channel_name) CHLTYPE(SVRCONN) SHARECNV(0)
Problem summary
**************************************************************** USERS AFFECTED: IBM i users of MQSUB over a channel connection. Platforms affected: IBM iSeries **************************************************************** PROBLEM DESCRIPTION: The MQSUB call in MQ is transactional in nature and will attempt to perform an internal commitment control when called. These transactions may sometimes fail when performed over a channel connection where multiplexing (Sharing Conversations) is enabled.
Problem conclusion
IBM MQ code has been modified to ensure that internal transactions invoked by MQSUB always have a valid transaction type. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.8 v9.0 CD 9.0.4 v9.0 LTS 9.0.0.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
SE67479
Reported component name
WMQ ISERIES V8.
Reported component ID
5724H7254
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-05
Closed date
2017-06-13
Last modified date
2017-06-13
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
WMQ ISERIES V8.
Fixed component ID
5724H7254
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
13 June 2017