3325193 - Impacts of JMS Shutdown Explained

Shutting down JMS consumers or senders (restart, undeployment/redeployment of the integration flow) can lead to the following - 

• Unexpected monitoring results / MPLs giving the impression of duplicate message processing or lost messages. This article tries to outline the unexpected, yet most-likely cases, and the reasons why the monitoring cannot capture the real situation at times.

• Message processing delays due to skipping message processing attempts

Example 1: Regular retry with subsequent success

The following picture outlines a usual JMS retry case, more precisely two failing attempts and a third attempt that succeeds. One unsuccessful retry attempt results in 2 MPL runs: the actual attempt and the subsequent move to the error queue to slow down the retry pace.


Figure 1.

Example 2: Immediate retry without processing attempt

The picture below is an example of a skipped processing attempt. The first run immediately moved the message to the error queue. The single run in RETRY state may not be confused with a processing attempt. Diving into the text view will also clarify what happened during which run. The second run depicts the first actual processing attempt, which also succeeds in this case. 

Figure 2.

Example 3: Interrupting commit/rollback

The last example outlines a successful message processing attempt, which masks itself behind a FAILED MPL and no subsequent retry attempt. If the message was already doing retries, the MPL may also remain in the RETRY state for the same reason (explained below), not showing additional runs. Usually, you’d expect a last COMPLETED run or additional retries to be performed. But this is not the case, if the message was actually processed successfully, while the MPL monitoring is not aware of its success.

Figure 3.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP Cloud Integration
• SAP Integration Suite
• SAP Business Technology Platform

CPI, HCI, SCPI, Integration Suite, Cloud Integration, JMS, shutdown, duplication, message loss, retry, commit, rollback, JMS adapter, XI adapter, AS2 adapter, Could not roll back JMS transaction due to Error rollback - internal error (transaction rollback is interrupted), Commit of JMS Transaction not possible due to Error committing - internal error (transaction commit is interrupted) , KBA , LOD-HCI-PI-CON-SOAP , SOAP Adapter , How To