APAR status
Closed as program error.
Error description
When attempting to set the MQ specific JMSDeliveryDelay property in the JMS transport headers, for example using the following ESQL: SET OutputRoot.JMSTransport.Transport_Folders.Header_Values.JMSDeliv eryDelay = 10000; The following exception is thrown: Number:INTEGER:4362 Text:CHARACTER:Class cast exception creating JMS Message Insert Type:INTEGER:5 Text:CHARACTER:Broker 'IIBv10'; Execution Group 'default'; Message Flow 'MessageDelivery_MF'; Node 'ComIbmJMSClientOutputNode' Exception Message ' java.lang.ClassCastException : java.lang.Integer incompatible with java.lang.String, Class cast exception creating JMS Message'; Exception Stack 'java.lang.ClassCastException: java.lang.Integer incompatible with java.lang.String at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterMbToJms.i mportHea dersDirect(Unknown Source) at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterMbToJms.i mportHea ders(Unknown Source) at com.ibm.broker.jmsclientnodes.JMSClientOutputNode.createOutputMe ssage(Un known Source) at com.ibm.broker.jmsclientnodes.JMSClientOutputNode.evaluate(Unkno wn Source) at com.ibm.broker.plugin.MbNode.evaluate(Unknown Source) ' Insert Type:INTEGER:5 Text:CHARACTER: Additionally it is not possible to use the schemaless mapping feature in the mapping node to map to this property.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus version 10 using the JMS Output node. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When attempting to set the MQ specific JMSDeliveryDelay property in the JMS transport headers, for example using the following ESQL: SET OutputRoot.JMSTransport.Transport_Folders.Header_Values.JMSDeliv eryDelay = 10000; The following exception is thrown: Number:INTEGER:4362 Text:CHARACTER:Class cast exception creating JMS Message Insert Type:INTEGER:5 Text:CHARACTER:Broker 'IIBv10'; Execution Group 'default'; Message Flow 'MessageDelivery_MF'; Node 'ComIbmJMSClientOutputNode' Exception Message ' java.lang.ClassCastException : java.lang.Integer incompatible with java.lang.String, Class cast exception creating JMS Message'; Exception Stack 'java.lang.ClassCastException: java.lang.Integer incompatible with java.lang.String at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterMbToJms.i mportHea dersDirect(Unknown Source) at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterMbToJms.i mportHea ders(Unknown Source) at com.ibm.broker.jmsclientnodes.JMSClientOutputNode.createOutputMe ssage(Un known Source) at com.ibm.broker.jmsclientnodes.JMSClientOutputNode.evaluate(Unkno wn Source) at com.ibm.broker.plugin.MbNode.evaluate(Unknown Source) ' Insert Type:INTEGER:5 Text:CHARACTER: There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
It is now possible to specify a delivery delay by setting the JMSDeliveryDelay transport header using ESQL like the example shown below: SET OutputRoot.JMSTransport.Transport_Folders.Header_Values.JMSDeliv eryDelay = 10000; If the JMS provider does not support the delivery delay property (for example for JMS 1.1 based providers) then a BIP8259 exception will be thrown. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.5 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT10078
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-15
Closed date
2017-05-09
Last modified date
2017-05-09
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
INTEGRATION BUS
Fixed component ID
5724J0530
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020