APAR status
Closed as user error.
Error description
Using the WebSphere MQ Java Message Service (WMQ JMS) V7.0.1.0 client, before a JMSObjectMessage is sent, attempting to set the JMSType by invoking the setJMSType() method on the ObjectMessage will result in an exception like: com.ibm.msg.client.jms.DetailedJMSException: JMSCMQ1006: The value for 'JMSType':'mcd://BLOB/' is not valid. The value 'mcd://BLOB/' for property 'JMSType' is not correct. Check the linked WebSphere MQ exception reason and completion code. being thrown.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This issue was reported by a user of WebSphere Message who was setting the JMSType of a Java compute node to mcd: A string starting with mcd:// is not allowed to be set by MQ the jmstype of an object message. Instead, when using WebSphere Message Broker, the jmstype on mqjmstranform node should be set to, for example, mcd://XMLNSC. This transform node constructs the JMS tree based on the input message and updates the message appropriately. The java compute node should not have the JMSType set to format mcd: User defined messages must be of type bytes in order for WebSphere MQ Java Message Service (JMS) client to process correctly. Text Messages are also acceptable and are considered a special case.
APAR Information
APAR number
IC68305
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED USE
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-30
Closed date
2010-11-16
Last modified date
2010-11-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"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