Request body exceeded max allowed content length

[nemethj]

Dear All, 

I need your help. We have an outbound rest call and sometimes we're receiving larger amount of data 95-100MB.

The payload is not sent to the instance, therefore the integration fails. 

05/09/19 05:23:39 (524) ECCSender.1 WARNING *** WARNING *** Request body exceeded max allowed content length
05/09/19 05:23:39 (524) ECCSender.1 WARNING *** WARNING *** RemoteGlideRecord failed to send data to https://xyzdev.service-now.com/ with (Request body exceeded max allowed content length)
05/09/19 05:23:39 (524) ECCSender.1 Attempt to send ecc_queue.70123e15dbd177406d50f9baae9619ca.1.xml failed: file remains enqueued for later sending

ECCSender.1 WARNING *** WARNING *** Deferring sending file ecc_queue.5c104a6ddb51b7406d50f9baae961982.xml - insufficient free memory (file length: 107496893. free memory: 152808488

I tried these:

- https://hi.service-now.com/kb_view.do?sysparm_article=KB0549558

- mid server config:

glide.mid.fast.responses = true
mid.eccq.max_payload_size = 210000000

- wrapper override:

wrapper.java.maxmemory=4096

- sys properties:

glide.rest.scripted.max_inbound_gzip_content_length_mb = 200
glide.rest.scripted.max_inbound_content_length_mb = 200

com.glide.attachment.max_size = 1024 (docs state it is 5MB and should not be increased, maybe they were old as it was already set by SN to this value.)

Also is there a way to kill a stuck job for the MID on the instance or on the MID itself? The scheduled job was turned off, and it still produced the rest call's results into the ECCSender folders. MID restart, Thread/ECC queue cleaning didn't help.

Thanks for any help!

Joe

[vinothkumar]

You can kill the job in the active transactions by navigating to user administrations > active transactions

Since it is outbound, you have to check outbound properties, since you have modified only inbound properties.

https://docs.servicenow.com/bundle/london-servicenow-platform/page/administer/notification/reference...

[nemethj]

Thx, but it is REST and not email related issue.