IT11889: START OF MESSAGE FLOW CONTAINING DECISIONSERVICE NODE FAILS WHEN CONFIGURED TO USE EXTERNAL RULES REPOSITORY USING DB2 10.5

APAR status

• Closed as program error.

Error description

• A 'java.lang.LinkageError' exception is seen when attempting to
  load a message flow which contains a DecisionService node and
  the DecisionServiceRepository Configurable Service is set to
  use a JDBC provider which is configured for DB2 10.5. Flow
  deployment works successfully, but the flow fails to load
  when the Integration Node is later restarted and the following
  BIP4157E and BIP4395E messages are seen in the system log:
  
  BIP4157E: ( MB9TEST.ODM ) The user-defined node ''<flow
  name>.Decision Service'' could not be deployed. Details:
  'java.lang.LinkageError: loading constraint violation: loader
  "com/ibm/broker/classloading/BusinessRulesClassLoader@d968ec52"
  previously initiated loading for a different type with name
  "org/w3c/dom/Document" defined by loader
  "com/ibm/oti/vm/BootstrapClassLoader@2c6811ce"' [21/10/2015
  15:19:25]
  
  BIP4395E: ( MB9TEST.ODM ) Java exception:
  ''java.lang.LinkageError'';
  thrown from class name: ''java.lang.ClassLoader'', method name:
  ''defineClassImpl'', file: ''ClassLoader.java'', line: '-2'
   [21/10/2015 15:19:25]
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V9.0 and V10.0 who use the
  DecisionService node with a DecisionServiceRepository
  configurable service to connect to an external rules repository.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A 'java.lang.LinkageError' exception is seen when attempting to
  load a message flow which contains a DecisionService node and
  the DecisionServiceRepository Configurable Service is set to
  use a JDBC provider which is configured for DB2 10.5. Flow
  deployment works successfully, but the flow fails to load
  when the Integration Node is later restarted and BIP4157E and
  BIP4395E messages are seen in the system log.
  
  This occurs because the BusinessRules classloader inside the
  Integration Node tries to load the system classes belonging to
  the org/w3c/dom package when they have already been loaded by
  the bootstrap classloader.
  
  
  <i>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</i>
  

Problem conclusion

• The BusinessRules classloader now delegates the loading of
  certain system classes to the bootstrap classloader.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.6
  v10.0      10.0.0.4
  
  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 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