Ecc_queue stuck at processing state for Rest Message via Mid server

[wclim]

Hi,

I encountered an issue regarding sending Rest Message via Mid server, and would like to see if anyone encountered this issue or am able to tell me what is wrong.

I was testing around some rest messages via mid server, using the Test functionality in the Rest Message

Everything was working fine and responses were coming in. But then one of the API (which was working fine previously, let's call this API X) returned an error message 

No response for ECC message request with sysid=XXXX after waiting for 60 seconds in ECC Queue

So I went into the ecc_queue table to check, and the related ecc_queue record was stuck in Processing state (even after few hours).

I tested the other rest APIs that was tested previously, but all of them got the No response message now. The related ecc_queue records were all stuck in Processing state too. 

The MID server itself is Up, and within the mid server itself, triggering APIs via cURL were all successful.

One thing i notice about the response from the triggering API X with the cURL is that the response is very large (about 80,000 characters). But the payload size in the ecc_queue has a limit of 1million character, so I'm not sure where the issue is.

Would appreciate any help in this issue.

Thanks!

[Sukraj Raikhraj]

is the payload too large or getting truncated, you can try increasing the size of the control that capture the payload that need to be process/

[wclim]

There is no indication that the payload is too large or truncated, using cURL to trigger the API directly in mid server returns the full response. In the Rest Message test functionality, it just states that  No response after 60 secs, and the ecc_queue record remains as processing.

And the payload field in the ecc_queue table is more than enough - it has a limit of 1million characters:

[Hitoshi Ozawa]

Have you tried deleting the stuck records from the ecc queue and retrying?

Just check the checkbox to the left of the records and select "delete" from the pull-down list at the bottom of the list.

Need to determine if it's something that always happens or if it something that just happened this once.

Also, have you checked the system log see if there was any error?

[wclim]

There are no errors in ServceiNow's system logs.

We tried the following: clearing the output_s folder in the mid server(there were alot of xml files being generated there), and then making sure none of the ecc_queue records are in procesing state.

After that, I was able to trigger the other API's successfully, but once I tested the API that returns a large response, the "No Response after 60 sec" message appears again, and the ecc_queue record became stuck at Processing state.

After that I wasn't able to trigger other API's (all of them got the No response message)