On 10.05.2012 11:24, Agnieszka Allstar wrote:
Obviously this has sth to do with the fact that in A case the mod_jk.log
says the request is recoverable, whereas in B case it's unrecoverable but I
can't really tell what's the cause after looking at mod_jk src.
Just in case you are still
I've spent few days trying to figure out what's going on but I give up.
I've tried boosting max_packet_size and few other properties but with no
success.
2012/4/30 Agnieszka Allstar allstar...@gmail.com
2012/4/30 Christopher Schultz ch...@christopherschultz.net
-BEGIN PGP SIGNED
Hello,
I'm using httpd 2.2.22 with mod_jk 1.2.32 and 2 load balanced tomcat
workers (TC 6.0.35). I have a question about recovery in case when active
worker becomes abruptly inactive.
Here's my test scenario:
1. Web service client sends SOAP request to apache server. This client
sends requests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kate,
On 4/30/12 7:06 AM, Agnieszka Allstar wrote:
Here's my test scenario: 1. Web service client sends SOAP request
to apache server. This client sends requests in 2 flavors, either
it is a generic SOAP call (A case) or a soap request with some
2012/4/30 Christopher Schultz ch...@christopherschultz.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kate,
On 4/30/12 7:06 AM, Agnieszka Allstar wrote:
Here's my test scenario: 1. Web service client sends SOAP request
to apache server. This client sends requests in 2 flavors, either
