APAR status
Closed as program error.
Error description
The customer have an application where they have: - created a connection and a session - created an asynchronous message consumer on that session (with associated message listener) - created a synchronous message consumer inside the onMessage method called by that asynchronous consumer, on the same session that was used to create the asynchronous consumer Any subsequent receive on that synchronous consumer returns null instead of a message, and each time outputs a message to the console: "Receive interrupted by async Session start"
Local fix
If customer want to use both asynchronous and synchronous consumers like this, separate sessions should be used for the different modes.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ JMS client version 8.0.0.2 and later who create an asynchronous consumer on a JMS session, associate a MessageListener with that consumer, then create a synchronous consumer in the onMessage method of that MessageListener using the same session the original asynchronous consumer was created with. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: If an application created an asynchronous consumer on a JMS session, associated a MessageListener with that consumer, then created a synchronous consumer in the onMessage method of that MessageListener using the same session the original asynchronous consumer was created with, any subsequent receive on that synchronous consumer would return null instead of a message, and each time output a message to the console: "Receive interrupted by async Session start"
Problem conclusion
When this is attempted, the synchronous receive will now throw an exception indicating that the application is contravening the JMS specification: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSCC0033: A synchronous method call is not permitted when a session is being used asynchronously: 'receive'. The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running. Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 v9.0 CD 9.0.1 v9.0 LTS 9.0.0.1 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
IT13758
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-12
Closed date
2016-05-31
Last modified date
2017-06-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
WMQ BASE MULTIP
Fixed component ID
5724H7251
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.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 June 2017