Topic: AJP Connection timeout results into jboss server crash

[rbutola]

Hello All,

We are facing a problem after configuring AJP connection timeout property in apache and respective connectiontimeout value in jboss server.xml file

We have apache 2.2.15, jboss 4.0.2 and mod_jk 1.2.25 configured on 64 bit windows 2003 OS and JDK 1.6.0.18.

JBoss application server is running as service.

After setting the timeout values for AJP, application service returns to stop state anytime (intermittently).

We have set a monitor for AJP connection and there are around 3-4 connections before service stops.

Configuration is as follow:

For workers.properties:

worker.list=worker2

worker.worker2.type=ajp13
worker.worker2.host=m.test.com
worker.worker2.connection_pool_timeout=60
worker.worker2.port=7019

For server.xml (Only AJP connector part):

<Connector port="7019" address="${jboss.bind.address}"
maxThreads="300" emptySessionPath="true" enableLookups="false" redirectPort="8443"
protocol="AJP/1.3" connectionTimeout="300000"/>

After rolling back the AJP timeout configuration, the problem has disappeared. But the number of AJP connections keep on increasing. We want AJP connections to be released after 5 mins.

Has anybody else seen such a strange behaviour? Any advice on possible resolution would be much appreciated.


Best Regards,
Rupendrasingh

[James Blond]

What is in the error log from catalia / tomcat about this issue?

[rem2500]

I see what sounds like the same issue as well with a very similar setup.

We see the AJP queues fill up and eventually, because they don't release the connections, the app has to be restarted.

Did you ever find a fix for this?

Thanks
Ben

[bambam]

The problem is you have set a connectionTimeout of 300000 which is 5 minutes and have not set one on the apache within the workers.properties

this creates an mismatch and the front end will close the connection but the backend will keep it open.

it is very important to make sure your numbers are in sync. note that the server XML uses ms where workers.properties uses seconds.

for example you need to add something like

worker.worker2.connection_pool_timeout=300

to match your front & backend

[rem2500]

Hi bambam,

Thanks for replying to my question. We are still seeing this issue a few times a week.

Currently in my server.xml we have:

connectionTimeout="600000"

And in our workers file we have:

connection_pool_timeout=600

So it looks like we have them synced. Is that time frame to high perhaps?

Thanks!