Resolution:
Description:

JMS queues used by BC for transport do not get consumed/cleared resulting in a huge backlog of messages. JMS queues in use are
Queue-1 = AX.BC.BC-tsa.RESPONDER.REQUEST
Queue-2 = AX.BC.BC-tsa.RESPONDER.ACK


Resolution:

The architecture of JMS differs in that there are separate queues for each of the inbound messages (.RESPONDER.ACK, .RESPONDER.INTERCHANGE, and .RESPONDER.REQUEST).  In order for a message to be taken off the queue, there must be a subscriber explicitly subscribing to the subject.  If you have no process starters configured in your BW private process to read these messages, the messages will stay on the queue forever, which is what you are seeing.  

Some BC protocols (such as EDI or SOAP) will generate a RESPONDER.ACK message to the JMS queue when BC successfully sends the response back to the trading partner.  

To remove data from the queue, create a process using the Receive Misc Message process starter in your BW project, and select the appropriate message type.  This will consume the messages off the queue.

BC Queues do not get consumed