Fixes are available
APAR status
Closed as program error.
Error description
A message sent by a WebSphere MQ (WMQ) Java client at v7 gets a character set error in the Java Message Service (JMS) layer from the WebSphere Application Server (WAS). The exception seen is ExtendedMessage: Entry; javax.jms.JMSException: MQJMS1006: invalid value for 'JMS_IBM_Character_Set': 'IBM-500'. at com.ibm.msg.client.wmq.v6.jms.internal.ConfigEnvironment. newException(ConfigEnvironment.java:431) at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer. sendInternal(MQMessageProducer.java:1153) at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer. send(MQMessageProducer.java:779) at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer. send(MQMessageProducer.java:2718) at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl. sendMessage(JmsMessageProducerImpl.java:894) at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl. send_(JmsMessageProducerImpl.java:749) at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl. send(JmsMessageProducerImpl.java:406) at com.ibm.mq.jms.MQMessageProducer. send(MQMessageProducer.java:299) at com.ibm.ejs.jms.JMSMessageProducerHandle. send(JMSMessageProducerHandle.java:1182) The same error is observed if the WebSphere MQ Java Message Service (JMS) client sets the character set explicitly on the outgoing message as: message.setStringProperty(JmsConstants.JMS_IBM_CHARACTER_SET, "IBM-500");
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ classes for JMS v7 sending messages to a WebSphere MQ v6 queue manager. The same erroneous behaviour is observed when a WebSphere MQ v6 JMS client is used to connect to a v6 or a v7 queue manager. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: The WebSphere MQ classes for JMS did not recognize the character set IBM-500 and hence treated it as a invalid character set.
Problem conclusion
The code has been modified so that the WMQ JMS implementation recognizes the character set IBM-500. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.4 -------- -------------------- Windows U200323 AIX U835793 HP-UX (PA-RISC) U836458 HP-UX (Itanium) U836463 Solaris (SPARC) U836459 Solaris (x86-64) U836465 iSeries tbc_p700_0_1_4 Linux (x86) U836460 Linux (x86-64) U836464 Linux (zSeries) U836461 Linux (Power) U836462 v6.0 Platform Fix Pack 6.0.2.11 -------- -------------------- Windows tbc_p600_0_2_11 AIX tbc_p600_0_2_11 HP-UX (PA-RISC) tbc_p600_0_2_11 HP-UX (Itanium) tbc_p600_0_2_11 Solaris (SPARC) tbc_p600_0_2_11 Solaris (x86-64) tbc_p600_0_2_11 iSeries tbc_p600_0_2_11 Linux (x86) tbc_p600_0_2_11 Linux (x86-64) tbc_p600_0_2_11 Linux (zSeries) tbc_p600_0_2_11 Linux (Power) tbc_p600_0_2_11 Linux (s390x) tbc_p600_0_2_11 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
IC69370
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-22
Closed date
2010-07-27
Last modified date
2010-07-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 WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R701 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.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023