PM84267: JDBC CONNECTIONS NOT COMMITTED AFTER JAVACOMPUTE NODE ONINITIALIZE

APAR status

• Closed as program error.

Error description

• After a JavaCompute node's onInitialize method is called the
  node framework should issue a commit on all JDBC connections on
  success, or issue a rollback in the event of an exception. This
  functionality was added by PM57754 but was not maintained after
  an internal restructure as a result of IC79446. The behaviour is
  also not present if just the jar file is deployed as this also
  causes the JavaCompute node to be reinitialized and onInitialize
  to be called again because the classloader has been refreshed.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker who make JDBC calls in a
  JavaCompute node onInitialize method.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  After a JavaCompute node's onInitialize method is called the
  node framework should issue a commit on all JDBC connections on
  success, or issue a rollback in the event of an exception. This
  functionality was added by PM57754 but was not maintained after
  an internal restructure as a result of IC79446. The behaviour is
  also not present if just the jar file is deployed as this also
  causes the JavaCompute node to be reinitialized and onInitialize
  to be called again because the classloader has been refreshed.
  

Problem conclusion

• WebSphere Message Broker has been modified so that a commit is
  issued on all JDBC connections after a JavaCompute node's
  onInitialize method completes successfully, or a rollback if
  it fails and throws an exception. This behaviour is consistent
  if a message flow is deployed or if a jar file is re-deployed
  with the message flow having already been deployed, both
  scenarios will now result in the appropriate commit/rollack call
  being made.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v7.0
  --------           --------------------
  Multiplatforms     7.0.0.6
  
  Platform           v8.0
  --------           --------------------
  Multiplatforms     8.0.0.3
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.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 in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  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

  5655V6000

Applicable component levels

• R700 PSY

     UP