How do I avoid the “ ‘Incorrect’ or ‘Unexpected’ event received: MExceptionEvent” error is thrown by the TIBCO Adapter (TM) for MQ Series Subscriber or Request-Response Service?
Article ID: KB0091467
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Adapter for Websphere MQ | - |
| Not Applicable | - |
Description
Resolution:
MExceptionEvent errors are thrown by the Inbound services when the message they are receiving from a BW process is not configured properly.
For Inbound services when the WireFormat is ActiveEnterpriseMessage with RV Transport and XMLMessage with JMS Transport, the services expect the incoming message or request to be ActiveEnterpriseFormat.
The usage of RV or JMS palettes to publish message or send request for the above configurations of adapter services results in the “MExceptionEvent” error since these palettes do not populate the AE fields in the message / request.
Workaround:
===========
Usage of ActiveEnterpriseAdapter palette is recommended for the above mentioned configurations since it creates a proper AE message as per the schema of the service.
The attached project mexcep.dat has an example process using JMS Queue Requestor, where the AE fields have been separately populated.
MExceptionEvent errors are thrown by the Inbound services when the message they are receiving from a BW process is not configured properly.
For Inbound services when the WireFormat is ActiveEnterpriseMessage with RV Transport and XMLMessage with JMS Transport, the services expect the incoming message or request to be ActiveEnterpriseFormat.
The usage of RV or JMS palettes to publish message or send request for the above configurations of adapter services results in the “MExceptionEvent” error since these palettes do not populate the AE fields in the message / request.
Workaround:
===========
Usage of ActiveEnterpriseAdapter palette is recommended for the above mentioned configurations since it creates a proper AE message as per the schema of the service.
The attached project mexcep.dat has an example process using JMS Queue Requestor, where the AE fields have been separately populated.
Issue/Introduction
How do I avoid the “ ‘Incorrect’ or ‘Unexpected’ event received: MExceptionEvent” error is thrown by the TIBCO Adapter (TM) for MQ Series Subscriber or Request-Response Service?
Attachments
Feedback
Yes
No
Powered by
