Is this the error in the SOAP::Lite module or I am using it the wrong way.
Yeah, 1.5GB seems like there might be a problem ... but not where, I doubt its within SOAP::Lite
perl -Mojo -e " b( shift )->slurp->b64_encode->say; int <>; " 49_678_352_bytesfile > 65M-b64ed
This takes about ~130mb on my machine, and around 20mb of that is perl -Mojo itself alone
I can't imagine SOAP::Lite tacking eleven times that amount, maybe one or three temporarily, but not eleven
Without mojo, with File::Slurp+SOAP::Lite, to slurp this 65M b64ed file takes about 74mb, 1500mb/74mb = 20 so still nowhere in the ballpark
I don't feel like looking into it past this; You can try
to see how much memory it takes to compose that request you're using -- shouldn't be 1.5 GB$soap->serializer()->envelope( method => 'DoThis', $param ),
I imagine it is the response that you're getting (your program is getting) to that request is an xml bomb ... or something else entirely
Also, what is a better way to make a SOAP call with large data
I imagine maybe https://metacpan.org/module/SOAP::Lite#ATTACHMENTS,
or even XML::Compile::XOP
but if your server doesn't accept that :)
Good luck
In reply to Re: Sending large file contents in SOAP call using SOAP::Lite
by Anonymous Monk
in thread Sending large file contents in SOAP call using SOAP::Lite
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |