APAR status
Closed as program error.
Error description
TryCatch nodes can be used to handle exceptions by propagating them to the catch terminal. Any node connected to the Catch terminal can process the ExceptionList message tree as part of handling the exception. If a JavaCompute node is wired to the Catch Terminal then it is possible that the Exception in the ExceptionList can be detached and added to one of the other message trees. For example: assembly.getExceptionList().getRootElement().detach(); assembly.getLocalEnvironment().getRootElement().addAsLastChild(e xceptionList); If flow processing returns to an earlier point in the flow before the TryCatch node then the elements attached to the message tree will go out of scope. The next node that attempts to process the corrupted tree will cause the Integration server to abend. The situation can also occur for the Check/Validate node, PEP Node, C Plugin nodes, Database and Filter nodes when propagating to their failure terminals.
Local fix
NA
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10.0 handling exceptions in a JavaCompute node following propagation from the catch terminal of the TryCatch node or the failure terminals of the Check/Validate, PEP, Database, Filter or C Plugin nodes. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Any node connected to the catch terminal of a TryCatch node or the failure terminal of either a Check/Validate node, PEP node, Database node, Filter node or C Plugin nodes can process the ExceptionList message tree as part of handling the exception. If a JavaCompute node is wired to the catch or failure terminals of these nodes then it is possible that the Exception in the ExceptionList can be detached and added to one of the other message trees. For example: assembly.getExceptionList().getRootElement().detach(); assembly.getLocalEnvironment().getRootElement().addAsLastChild(e xceptionList); If flow processing returns to an earlier point in the flow before the node that first propagated to the catch/failure terminal then the elements attached to the message tree will go out of scope. The next node that attempts to process the corrupted tree will cause the Integration Server (execution group) to abend.
Problem conclusion
The product has been corrected so that the ExceptionList is correctly setup and will not be descoped in this situation. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.9 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
IT19345
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
2017-02-21
Closed date
2017-05-25
Last modified date
2017-05-25
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