PI08962: MBELEMENT.COPY() DOES NOT PASS BACK EXCEPTIONS TO JAVA

APAR status

• Closed as program error.

Error description

• This problem occurs when using a Java Compute node or a Java
  plugin node.
  The MbElement class in the Java plugin API contains a copy()
  method. This method, according to the product documentation, can
  throw an MbException.
  However, if an exception occurs (commonly a parser exception)
  while performing the underlying copy, this exception is not
  handled correctly.
  Specifically, this exception does not get thrown back, as an
  MbException, to your Java code.
  The result is that an unhandled exception exists in the runtime,
  causing the execution group to restart or abend.
  

Local fix

• This can be worked around by fully parsing the message before
  performing the copy. For example, by setting parse timing on the
  input node to Immediate rather than On Demand. This will flush
  out any parsing exceptions prior to the MbElement.copy()
  invocation.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker and IBM Integration Bus
  who use the MbElement.copy() method in a Java Compute node or
  Java plugin node.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  The problem occurs when using a Java Compute node or a Java
  plugin node.
  The MbElement class in the Java plugin API contains a copy()
  method. This method, according to the product documentation, can
  throw an MbException.
  
  However, if an exception occurs (commonly a parser exception)
  while performing the underlying copy, this exception is not
  handled correctly.
  
  Specifically, this exception does not get thrown back, as an
  MbException, to your code.
  The result is that an unhandled exception exists in the runtime,
  causing the execution group to restart or abend.
  
  
  
  
  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 ensures that exceptions get passed back from the
  copy() method to your Java code, where they can be handled
  within that node or allowed to follow the usual message flow
  exception handling procedure.
  
  Version 7 of the product is fixed under APAR PI24856.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.5
  v9.0       9.0.0.2
  
  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

  WEB MB Z/OS

• Fixed component ID

  5697P4400

Applicable component levels

• R800 PSY

     UP