APAR status
Closed as program error.
Error description
The JMSOutput Node determines if the JMS destination passed in the destination list is a queue or a topic by testing it by casting to the correct destination type. It then uses either getTopicName() or getQueueName() to determine the name of the destination and uses this value as a key to lookup cached MessageProducers. In the case of WebLogic it is possible for a Destination to be assignable to a Topic however the getTopicName() method returns null. This causes the key "null" to be used to lookup the Message Producer instead of the real queue or topic name and results in all messages in the destination list being sent to the same Destination.
Local fix
NA
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v9.0 or higher using the JMSOutput Node to connect to a WebLogic JMS server. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The JMSOutput Node determines if the JMS destination passed in the destination list is a queue or a topic by testing it by casting to the correct destination type. It then uses either getTopicName() or getQueueName() to determine the name of the destination and uses this value as a key to lookup cached MessageProducers. In the case of WebLogic it is possible for a Destination to be assignable to a Topic however the getTopicName() method returns null. This causes the key "null" to be used to lookup the Message Producer instead of the real queue or topic name and results in all messages in the destination list being sent to the same Destination. 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
The JMSOutput Node can now cope with destinations which are assignable to a topic, but do not return a valid topic name. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 9.0.0.6 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
IT13102
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
2016-01-11
Closed date
2016-05-24
Last modified date
2016-05-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
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