APAR status
Closed as program error.
Error description
At 10.0.0.7 the kafka nodes have shipped a new copy of the slf4j logging framework jars. These jars do not tolerate being loaded multiple times, and therefore attempting to use the activeMQ lib directory as a jarsURL for a JMSProvider configurable service causes the following exception to appear in the stdout log at 10.0.0.7: 2016-12-05 16:15:45.452 1 SLF4J: Class path contains multiple SLF4J bindings. This can lead to the following exception in the syslog: Dec 5 15:47:55 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 3/3) BIP4395E: Java exception: 'java.lang.LinkageError'; thrown from class name: 'org.slf4j.LoggerFactory', method name: 'getILoggerFactory', file: 'LoggerFactory.java', line: '332' Dec 5 15:47:56 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 1/3) BIP2628W: Exception condition detected on input node 'activeMQTest.JMS Input'. Dec 5 15:47:56 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 2/3) BIP4367E: The method 'run' in Java node 'JMS Input' has thrown the following exception: java.lang.NoClassDefFoundError: org.apache.activemq.ActiveMQConnectionFactory (initialization failure).
Local fix
Place the activeMQ "all client" jar in a different location and the update the JMS configurable services jarsURL property to reference this new location.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus version 10.0.0.7 using the JMS nodes. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: At 10.0.0.7 the kafka nodes have shipped a new copy of the slf4j logging framework jars. These jars do not tolerate being loaded multiple times, and therefore attempting to use the activeMQ lib directory as a jarsURL for a JMSProvider configurable service causes the following exception to appear in the stdout log at 10.0.0.7: 2016-12-05 16:15:45.452 1 SLF4J: Class path contains multiple SLF4J bindings. This can lead to the following exception in the syslog: Dec 5 15:47:55 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 3/3) BIP4395E: Java exception: 'java.lang.LinkageError'; thrown from class name: 'org.slf4j.LoggerFactory', method name: 'getILoggerFactory', file: 'LoggerFactory.java', line: '332' Dec 5 15:47:56 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 1/3) BIP2628W: Exception condition detected on input node 'activeMQTest.JMS Input'. Dec 5 15:47:56 creatorsMastertape IIB[32598]: IBM Integration Bus v10007 (BRK10.default) [Thread 336] (Msg 2/3) BIP4367E: The method 'run' in Java node 'JMS Input' has thrown the following exception: java.lang.NoClassDefFoundError: org.apache.activemq.ActiveMQConnectionFactory (initialization failure). 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 product now loads the SLF4J classes from a single known location in the product install. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.8 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
IT18256
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-06
Closed date
2017-03-16
Last modified date
2017-03-16
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
5724J0540
Applicable component levels
RA00 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":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020