Fixes are available
APAR status
Closed as program error.
Error description
When a WebSphere MQ Version 7 Java Message Service (JMS) client application creates a transacted JMS session, sends a message to a Version 6 queue manager and then commits the unit of work, the message is actually rolled back.
Local fix
Pass a valid destination object while creating the QueueSender object. Queue queue = session.createQueue("QName"); QueueSender sender = session.createSender(queue); sender.send(message); The above code will ensure the message gets committed when session.commit() is invoked.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects any WebSphere MQ Version 7 JMS application that sends messages to a Version 6 queue manager using transacted sessions. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: This problem occurs when Java Message Service (JMS) applications create a QueueSender object passing in a null value, and then specifies the actual destination where the message will be sent when calling the QueueSender.send() method. Some example code is shown below: QueueSender sender = session.createSender(null); sender.send(session.createQueue(queue), message); When a QueueSender is created passing a null value, the QueueServices that are required for point-to-point messaging are not initialized. This results in problems later on committing the messages.
Problem conclusion
In order to fix this problem, the JMS Client has been changed to initialize the QueueServices just before the first message is sent by a QueueSender. This prepares the JMS Client for point-to-point messaging, and ensures that attempts to commit messages that have been sent will succeed. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.0 -------- -------------------- Windows U200306 AIX U823774 HP-UX (PA-RISC) U823665 HP-UX (Itanium) U823667 Solaris (SPARC) U823772 Solaris (x86-64) U824344 iSeries tbc_p700_0_1_0 Linux (x86) U823664 Linux (x86-64) U823773 Linux (zSeries) U823668 Linux (Power) U823666 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
IC60117
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-20
Closed date
2009-03-12
Last modified date
2011-08-24
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 WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023