APAR status
Closed as program error.
Error description
When using the CallableFlowAsyncInvoke and CallableFlowAsyncResponse nodes with the AgentX callable flow agent configured: if an exception occurs while trying to invoke a remote flow, e.g. the specified endpoint does not exist, then the following abend will occur: #7 ImbAbendSignalHandler from /opt/mqsi/iib-10.0.0.17/server/lib/libCommonServices.dylib #8 _sigtramp from /usr/lib/system/libsystem_platform.dylib #9 ?? #10 abort from /usr/lib/system/libsystem_c.dylib #11 ImbCallableFlowManager::FlowReplyCallbackAsyncLocal::setResponse (ImbException const&) from /opt/mqsi/iib-10.0.0.17/server/lib/libCallableFlow.dylib #12 ImbCallableFlowManager::errorToFlowCaller(ImbBufferedStringBase< unsigned char, std::__1::char_traits<unsigned char>, unsigned short, 24u, 128u>, ImbWstring, int, int, ImbWstring) from /opt/mqsi/iib-10.0.0.17/server/lib/libCallableFlow.dylib #13 ImbCallableFlowRemote::remoteReplyErrorInner(ImbWstring const&, ImbWstring, int, int, ImbWstring) from /opt/mqsi/iib-10.0.0.17/server/lib/libCallableFlow.dylib #14 ImbCallableFlowRemote::remoteReplyCallback(v8::FunctionCallbackI nfo<v8::Value> const&) from /opt/mqsi/iib-10.0.0.17/server/lib/libCallableFlow.dylib This is instead of the correct behaviour which is an exception should be propagated out of the Failure terminal of the CallableFlowAsyncResponse node. Secondly, if a CallableFlowAsyncResponse node processes an exception response then the next non-exception response processed by the node will cause the following abend to occur: #1 ImbTimeStampBase::operator=(ImbTimeStampBase const&) /opt/mqsi/iib-10.0.0.17/server/lib/libMessageServices.dylib #2 ImbGmtTimeStamp::operator=(ImbGmtTimeStamp const&) /opt/mqsi/iib-10.0.0.17/server/lib/libMessageServices.dylib #3 ImbMessage::setReceiveTime(ImbGmtTimeStamp const&) /opt/mqsi/iib-10.0.0.17/server/lib/libMessageServices.dylib #4 ImbCallableFlowAsyncResponseNode::buildMessageAssembly(ImbCallab leTemplateNode::ExecutionInstance&, ImbDefaultProperties&, ImbMessageOptions const&, ImbWstring const&, ImbMessage&, ImbMessage&, ImbMessage&) /opt/mqsi/iib-10.0.0.17/server/lib/libCallableFlow.dylib #5 ImbInputTemplateNode::processData(ImbOsThread*, bool, ImbCallableTemplateNode::ExecutionInstance&, ImbMqConnection*, bool&, bool, ImbInputTemplateNode::ParmsHolder&, bool&, ImbDefaultProperties&, ImbCallableTemplateNode::OrderToken&, ImbInputTemplateNode::ReadDataRC) /opt/mqsi/iib-10.0.0.17/server/lib/libTemplateNodes.dylib #6 ImbInputTemplateNode::eventProcessingRun(ImbOsThread*, bool, ImbCallableTemplateNode::ExecutionInstance&, ImbMqConnection*, bool&, bool, ImbInputTemplateNode::ParmsHolder&, bool&, ImbDefaultProperties&, ImbCallableTemplateNode::OrderToken&) /opt/mqsi/iib-10.0.0.17/server/lib/libTemplateNodes.dylib #7 ImbInputTemplateNode::runInternal(ImbOsThread*, bool, int) /opt/mqsi/iib-10.0.0.17/server/lib/libTemplateNodes.dylib #8 ImbInputTemplateNode::run(ImbOsThread*, bool) /opt/mqsi/iib-10.0.0.17/server/lib/libTemplateNodes.dylib #9 ImbInputTemplateNode::Parameters::run(ImbOsThread*) /opt/mqsi/iib-10.0.0.17/server/lib/libTemplateNodes.dylib #10 ImbThreadPoolThreadFunction::run(ImbOsThread*) /opt/mqsi/iib-10.0.0.17/server/lib/libCommonServices.dylib #11 ImbOsThread::threadRun() /opt/mqsi/iib-10.0.0.17/server/lib/libCommonServices.dylib #12 ImbOsThread::threadBootStrap(void*) /opt/mqsi/iib-10.0.0.17/server/lib/libCommonServices.dylib #13 _pthread_body (libsystem_pthread.dylib:x86_64+0x32ea) #14 _pthread_start (libsystem_pthread.dylib:x86_64+0x6248) #15 thread_start (libsystem_pthread.dylib:x86_64+0x240c)
Local fix
N/A
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10 and App Connect Enterprise v11 using the CallableFlowAsyncInvoke and CallableFlowAsyncResponse nodes. Platforms affected: MultiPlatform, z/OS **************************************************************** PROBLEM DESCRIPTION: When using a pair of CallableFlowAsyncInvoke and CallableFlowAsyncResponse nodes to make a Remote Only invocation an abend will occur if the AgentX callable flow agent raises an exception. This could happen if the requested application or endpoint name is invaild, not deployed, or inactive. Additionally if an exception is propagated by a CallableFlowAsyncRespone node either as an exception response from the invoked flow or an exception from the AgentX callable flow agent then the next non-exception response to be processed by the same thread in that node will cause an abend.
Problem conclusion
The CallableFlowAsyncResponse node can now correctly handle exceptions arising from the AgentX callable flow agent and correctly cleans up after processing an exception in the node to prevent both abends. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.18 v11.0 11.0.0.5 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
IT29341
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
2019-06-05
Closed date
2019-09-30
Last modified date
2019-10-02
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
[{"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:
02 October 2019