A fix is available
APAR status
Closed as program error.
Error description
An application using the WebSphere MQ V7 classes for JMS that is communicating with a WebSphere MQ V7 queue manager creates many FDCs with Probe ID XS001007. The data portion of the FDC contains the following information: | insert constants :- XMSC_INSERT_QUEUE_MANAGER, XMSC_WMQ_CONNECTION_MODE, XMSC_WMQ_HOST_NAME | message id :- JMSWMQ0019
Local fix
Local Fix￘ n/a
Problem summary
**************************************************************** USERS AFFECTED: This issue affects two categories of users: 1: Users of: - The WebSphere MQ V7.0.1 classes for JMS. - The WebSphere MQ V7.0.1 Resource Adapter. - The WebSphere MQ V7.0.1 OSGi bundles. - The WebSphere Application Server V7.0 WebSphere MQ messaging provider. - The WebSphere Application Server V8.0 WebSphere MQ messaging provider. - The WebSphere Application Server V6.1 WebSphere MQ messaging provider who have configured the WebSphere variable MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0.1 installation. who have applications that connect to a WebSphere MQ V7 queue manager using WebSphere MQ messaging provider normal mode, and then receive a JMSException containing the message: JMSWMQ0019 : Failed to disconnect from queue manager <queue_manager> using connection mode <connection_mode> and host name 'null'. when the application calls the one of the methods shown below: - JMSConnection.close() - JMSSession.close() 2. Users of: - The WebSphere Application Server V7.0 WebSphere MQ messaging provider. - The WebSphere Application Server V8.0 WebSphere MQ messaging provider. - The WebSphere Application Server V6.1 WebSphere MQ messaging provider who have configured the WebSphere variable MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0.1 installation. who have WebSphere Application Server Listener Ports that connect to a WebSphere MQ V7 queue manager using WebSphere MQ messaging provider normal mode. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java +Java zOS **************************************************************** PROBLEM SUMMARY: When one of the following events occurs: - An application closes a JMS Connection by calling the method Connection.close(). - An application calls the method Session.close() to close a JMS Session. - The WebSphere Application Server Connection Manager closes a WebSphere MQ messaging provider JMS Connection that was an application server Connection Pool. - The WebSphere Application Server Connection Manager closes a WebSphere MQ messaging provider JMS Session that was in an application server Session Pool. the WebSphere MQ classes for JMS (used internally by the WebSphere Application Server MQ messaging provider) disconnect the JMS Connection or JMS Session from the WebSphere MQ queue manager that they were connected to. To do this, the WebSphere MQ classes for JMS call the WebSphere MQ API MQDISC. If the disconnect operation fails (for example, because the queue manager has been stopped), the WebSphere MQ classes for JMS throw a JMSException containing the message: JMSWMQ0019 : Failed to disconnect from queue manager '<queue_manager>' using connection mode '<connection_mode>' and host name '<hostname>'. This exception is either returned to the application, or logged by the WebSphere Application Server Connection Manager. When constructing the JMSWMQ0019 message that was contained within the JMSException, the WebSphere MQ classes for JMS looked up the message text, and provided some insert data that would be inserted into the message at the appropriate points. The insert data consisted of a series of name/value pairs, containing: - The insert name. - The data which should be inserted into the message text. As a result of the code changes for APAR IV00348, the wrong insert name was specified by the WebSphere MQ classes for JMS when they created the JMSException. This caused the WebSphere MQ classes for JMS to generate an FDC containing Probe Identifier XS001007 and message identifier JMSWMQ0019. The JMSException was still returned either to the application, or logged by the WebSphere Application Server Connection Manager. However, the word "null" was displayed after the hostname, so the message in the JMSException always had the form: JMSWMQ0019 : Failed to disconnect from queue manager '<queue_manager>' using connection mode '<connection_mode>' and host name 'null'. With the exception that the FDC was being generated, there was no functional change in behaviour within the WebSphere MQ classes for JMS. That is to say that the the classes behaved in the same functional manner to the scenario where the FDC would not have been generated if the code change associated with IV00348 had used the correct data insert name value.
Problem conclusion
The WebSphere MQ classes for JMS have been updated to specify the correct insert names when generating JMSExceptions containing the JMSWMQ0019 message. This change means that the FDC reported in this APAR will no longer be generated. The JMSWMQ0019 message contained within the JMSException will also contain information about the hostname of the machine where the queue manager was running when the disconnect operation failed. The message in the JMSException now looks like this: JMSWMQ0019 : Failed to disconnect from queue manager '<queue_manager>' using connection mode '<connection_mode>' and host name '<hostname>'. | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0006 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0006 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0006 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0006 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0006 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0006 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0006 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0006 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0006 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0006 | | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0007 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0007 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0007 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0007 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0007 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0007 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0007 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0007 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0007 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0007 | | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0008 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0008 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0008 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0008 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0008 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0008 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0008 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0008 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0008 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0008 | | MDVREGR 7.0.1-WS-MQ-AixPPC64-FP0009 | | MDVREGR 7.0.1-WS-MQ-HpuxIA64-FP0009 | | MDVREGR 7.0.1-WS-MQ-HpuxPaRISC64-FP0009 | | MDVREGR 7.0.1-WS-MQ-LinuxIA32-FP0009 | | MDVREGR 7.0.1-WS-MQ-LinuxPPC64-FP0009 | | MDVREGR 7.0.1-WS-MQ-LinuxS390X-FP0009 | | MDVREGR 7.0.1-WS-MQ-LinuxX64-FP0009 | | MDVREGR 7.0.1-WS-MQ-SolarisSparc64-FP0009 | | MDVREGR 7.0.1-WS-MQ-SolarisX64-FP0009 | | MDVREGR 7.0.1-WS-MQ-Windows-FP0009 | --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.10 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
IV25244
Reported component name
WMQ SOL SPARC
Reported component ID
5724H7223
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-25
Closed date
2012-09-14
Last modified date
2013-11-27
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 SOL SPARC
Fixed component ID
5724H7223
Applicable component levels
R701 PSY
UP
[{"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:
03 October 2021