Why do I get the error "AESDKC-0131, Category = Rpc, Severity = errorRole, Description = Unexpected reply received" while running TIBCO Adapter (TM) for MQ Series Request-Response Invocation service with JMS Transport?
book
Article ID: KB0090271
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix Adapter for Websphere MQ
-
Not Applicable
-
Description
Resolution: Description: ========= This error is thrown because the 'closure' and 'userClosure' fields in the reply message have to be populated properly in BW's 'Respond to Adapter' palette.
Workaround: ========== When RRI service is configured with JMS Transport, the 'closure' and userClosure' fields have to be explicitly mapped in "Binary" format.
Please refer to the RespondToAdapterRequest task -> Input tab and caret_closure_caret and caret_UserClosure_caret fields in the BW process in a project with RRI configured. Their types have to be modified to binary. The attached Word doc gives an overview of how to map the closure data properly.
The closure node(s) contain MQSeries message specific information and if not mapped properly we can expect an error while the adapter tries to put the reply message back to the reply queue.
Issue/Introduction
Why do I get the error "AESDKC-0131, Category = Rpc, Severity = errorRole, Description = Unexpected reply received" while running TIBCO Adapter (TM) for MQ Series Request-Response Invocation service with JMS Transport?
Attachments
Why do I get the error "AESDKC-0131, Category = Rpc, Severity = errorRole, Description = Unexpected reply received" while running TIBCO Adapter (TM) for MQ Series Request-Response Invocation service with JMS Transport?
get_app