Tuesday, 28 May 2013

ICM_HTTP_CONNECTION_FAILED

This blog describes about "ICM_HTTP_CONNECTION_FAILED" during outage or no outage:

If in case, you receive error message stating that  "ICM_HTTP_CONNECTION_FAILED" in SMQ2. I request everyone to follow the steps mentioned below. Sometimes, this error can lead to potential P1's in PI.

Note: Before proceeding to the below steps, please check whether the messages are stuck due to any weekend outage. If "Yes", then proceed with Issue 1 (steps), if "No" continue Issue 2 (Steps).

Issue 1: During Outage ("ICM_HTTP_CONNECTION_FAILED")

If in case, any messages stuck in (SMQ2) and error message displayed as "ICM_HTTP_CONNECTION_FAILED".
Action to be performed:

Step 1: Inform Basis  (Messages stuck in SMQ2 due to Outage)

Step 2: Inform Business (Messages stuck in SMQ2 due to Outage)

Step 3: After outage completion, refresh SMQ2. After that, Messages will be getting processed successfully in Production system.

Step 4: Inform Business & Basis stating that ( Messages processed successfully after the outage)
Issue 2: No Outage ("ICM_HTTP_CONNECTION_FAILED")

If in case any messages stuck in  (SMQ2) and if the error message displayed as "ICM_HTTP_CONNECTION_FAILED".
Action to be performed:

Step 1: Inform Basis (Messages stuck in SMQ2)

Step 2: Inform Business  (Messages stuck in SMQ2 and basis team is working on this issue)

Send consolidated list for the particular day:

1. Processed message list
2. Errored message list
3. Synchronous message list
4. Scheduled message list
5. Scheduled for outbound processing message list
6. Check Last message processed in production system and (inform to Business and CC to Manager, TL accordingly)

Step 3: After soap adapter refresh and AF core refresh, all the message will be processed

Step 4: Inform Business & Basis (After soap adapter refresh and AF core refresh, all the messages processed successfully)

No comments:

Post a Comment