IT12745: JAVA NODE ONDELETE() ERRORS CAN CAUSE ABENDS DURING DEPLOYMENT

APAR status

• Closed as program error.

Error description

• If the onDelete() method of a Java node (such as the JMS nodes)
  throws an exception whilst the message flow/node is being
  deleted, then the integration server can unexpectedly terminate
  with an abend or core dump.
  A message flow/node can be deleted during a normal redeploy,
  un-deploy, or reconfiguration activity.
  The abend shows the following stack:
  
  (0x05f8f980+0x00000120) __dt__18ImbDataFlowManagerFv
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  (0x06169180+0x000004e0)
  removeDataFlowFromList__24ImbDeployedResourceGroupFRC10ImbWstrin
  g
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  (0x06169980+0x000000b8)
  rollbackChangedFlows__24ImbDeployedResourceGroupFv
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  (0x061ad900+0x000004ac) rollback__22ImbDataFlowApplicationFv
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  (0x061bb480+0x000000e4) rollback__25ImbExecutionGroupDirectorFv
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  (0x06155280+0x000000a0)
  rollback__Q2_23ImbConfigurationManager11TransactionFv
  [/opt/IBM/mqsi/lib/libMessageServices.a(libMessageServices.a.so)
  ]
  .
  The abend is caused by incorrect handling of the exception that
  is thrown by the onDelete() method.
  

Local fix

• Investigate the cause of the exception being thrown from the
  onDelete() method of the Java node, and resolve that problem so
  that the exception is no longer thrown.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v9.0 with JavaCompute nodes
  that have implemented an onDelete() method.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the onDelete() method of a JavaCompute node throws an
  exception, then the exception is not correctly handled by the
  integration server. The exception can cause memory leaks,
  errors, or crashes as it results in the corruption of in-memory
  configuration information. These problems can occur on a
  deployment, redeployment, or un-deployment.
  

Problem conclusion

• The product now catches exceptions thrown from the onDelete()
  method and logs an error.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0       9.0.0.6
  
  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