How to consume pending ResponderInterchange messages in a JMS queue.
Article ID: KB0087736
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
TIBCO BusinessConnect™ sends the ResponderInterchange message to the private process when it receives an interchange from the trading partner. When using JMS as transport, the JMS Queue Name is AX.BC.<installation-name>.RESPONDER.INTERCHANGE and the Message Name is
InboundInterchangeLoggedToFile. If there is no private process configured to consume these pending messages, this message queue will grow continuously, and consume system resources.
Environment:
============
o TIBCO BusinessConnect™ 5.2.1
o TIBCO BusinessConnect™ EDI Protocols 5.3.0
Resolution:
===========
Use Receive Misc. Msg activity in Designer to consume these messages. When configuring the message name for Receive Misc. Msg activity, choose 'interchangeloggedtofile'.
Description:
============
TIBCO BusinessConnect™ sends the ResponderInterchange message to the private process when it receives an interchange from the trading partner. When using JMS as transport, the JMS Queue Name is AX.BC.<installation-name>.RESPONDER.INTERCHANGE and the Message Name is
InboundInterchangeLoggedToFile. If there is no private process configured to consume these pending messages, this message queue will grow continuously, and consume system resources.
Environment:
============
o TIBCO BusinessConnect™ 5.2.1
o TIBCO BusinessConnect™ EDI Protocols 5.3.0
Resolution:
===========
Use Receive Misc. Msg activity in Designer to consume these messages. When configuring the message name for Receive Misc. Msg activity, choose 'interchangeloggedtofile'.
Issue/Introduction
How to consume pending ResponderInterchange messages in a JMS queue.
Feedback
Yes
No
Powered by
