Internal Server Error 500, RemoteGlideRecord failed to send data request body exceeded max allowed content length issue on mid server

Todd O
Tera Guru

‎03-08-2020 10:01 AM

I am pulling a large amount of data over my mid server (93MB file) and I'm getting the error below in my mid server log file (see first image below). My ServiceNow instance ecc_queue ouput record just hangs in state of "processing." I need to be able to occasionally run this large data pull and need to find a solution around this 

Originally, I was getting this error ( ECCSender.1 SEVERE *** ERROR *** Payload size of 93097306 bytes exceeded maximum of 20000000 bytes.) I solved that by adding a property on my Mid server called mid.eccq.max_payload_size and set that well above my payload size (see second image below for that). After that was solved, it appears an exception is being thrown when the Mid server attempts to send the file to the server in that the Request Body exceeds max allowed content.

[FYI: (forum post) (HI post reference too) about resolving the max_payload size]

I thought a "payload.txt" file would be added automatically when the size is so large. Is that a configuration setting possibly I can set so that it just attaches my 93MB file instead of throwing 500 Internal Server error? I have property called glide.soapprocessor.large_field_patch_max set to default 512,000 but apparently that's not triggering it.

Mid Server error in Log filefind_real_file.png

Original Problem that I fixed screen shot:find_real_file.png

Labels:
Preview file
27 KB
Preview file
37 KB
0 Helpfuls
  • 1,668 Views
2 REPLIES 2

Sukraj Raikhraj
Kilo Sage

‎03-08-2020 12:18 PM

what's the attachment payload size? increase the attachment size and that could possible resolved this issue.

0 Helpfuls

Todd O
Tera Guru
In response to Sukraj Raikhraj

‎03-08-2020 02:18 PM

Hi Sukraj, see my second paragraph above. The payload size is "Payload size of 93097306." I've added the "mid.eccq.max_payload_size" mid server entry and it has no impact - even after re-starting the mid server. You can add this as a property or a configuration parameter for the mid server and I've tried both. Each time I restarted the mid server (both from instance as well as the actual server). I still get the same results. 

p.s., the value that I set mid.eccq.max_payload_size was 95000000 which was several MB higher than my payload size. I'm baffled why this setting is having no impact on behavior.

0 Helpfuls