Re: [SPAM] RE: Application stops responding, jk worker in error state

2010-06-19 Thread Rainer Jung
On 19.06.2010 03:46, Neil Aggarwal wrote: Rainer: Hmmm, errno 11 is often EAGAIN. What platform are you using (OS, version)? I am using CentOS 5.5 freshly installed, not an upgrade. I tried that as a fix to this problem. I wiped the server clean and reinstalled everything from scratch. It

RE: Application stops responding, jk worker in error state

2010-06-19 Thread Neil Aggarwal
Rainer: would you mind opening an issua in Bugzilla, attaching your log snippet and possibly your workers.properties I created bug 49468 in bugzilla, included my log snippet and attached the workers.properties file. You can also open a second issue concering the obvisouly wrong

RE: Application stops responding, jk worker in error state

2010-06-18 Thread Neil Aggarwal
Rainer: If you are going to post part of your log file, please also do provide your mod_jk configuration and version information. I am using mod_jk 1.2.30 which I built from the source tarball. My application just locked up so I did a tail -f on the mod_jk log and made a request to it.

RE: Application stops responding, jk worker in error state

2010-06-18 Thread Neil Aggarwal
Rainer: I am attaching the properties for my jk configuation and a screen shot of the JK Status in case it helps. It looks like the mailing list software stripped the attachments from my email. Here is the list of jk properties: worker.server_name=tweb1.retcgroup.com worker.server_port=80

Re: Application stops responding, jk worker in error state

2010-06-18 Thread Rainer Jung
On 18.06.2010 22:44, Neil Aggarwal wrote: Rainer: If you are going to post part of your log file, please also do provide your mod_jk configuration and version information. I am using mod_jk 1.2.30 which I built from the source tarball. My application just locked up so I did a tail -f on the

RE: Application stops responding, jk worker in error state

2010-06-18 Thread Neil Aggarwal
Rainer: Hmmm, errno 11 is often EAGAIN. What platform are you using (OS, version)? I am using CentOS 5.5 freshly installed, not an upgrade. I tried that as a fix to this problem. I wiped the server clean and reinstalled everything from scratch. It was on CentOS 5.4 before and I had the same