|The stupid question is the question not asked|
Solved: Software caused connection abort in mod_perl + SOAP::Lite + Apache environmentby sam_bakki (Pilgrim)
|on Nov 14, 2013 at 13:24 UTC||Need Help??|
sam_bakki has asked for the
wisdom of the Perl Monks concerning the following question:
I have been developing a framework with using SOAP::Lite. Basically, Server exposes set of APIs via SOAP and clients will consume the APIs via SOAP. Both server code (framework code, its huge) and client code (many clients, small ones) are written in perl.
Everything works fine , until we started performance testing. We have started 55 clients at a time (using windows start command) so at a time 55 clients will be working with the Server SOAP framework.
I had a look into the server returned XML , Which was in complete. So the XML parser failed.
I have extensive logging mechanism in my server code (using Log4Perl) but nothing useful was reported. Then I looked in to Apache logs, I found
Edit: Some times I see the following error as well in Apache log
The number of above "Software Caused connection" errors was matched with the number of Clients failed.
When I run the clients with 5 seconds delay , Everything works fine. So I face this issue when I do it in parallel.
Any one had the similar issue with Apache + mod_perl? How to overcome?
Edit: Problem is solved . As per the pointer given from a veteran monk, I have increased Apache's timeout and it solves the issue. Thanks Monk
Thanks & Regards,