AJP and JMX ordering

[analogueboy]

I'm having a problem on an application which is related to the startup, Tomcat starts and opens the AJP port 8009 so the Apache webservers start forwarding new requests to it thinking that it is ready. However, my application doesn't deploy in time which gives me the folloewing problem "MAPPING configuration error for request URI xxxxx".

Does AJP notify the webservers when the port is opened, or will a standard load-balancing worker2.properties keep trying every IP adress regardless of the status of the box? Has anyone else come across this problem and found a way to prevent the application server from serving requests until all services have started?

Any help would be greatly appreciated because we currenly have to take down the whole cluster to restart our application :(

[starksm64]

In 3.2.5 the ajp connector is not started until the server is started and all web apps have been deployed.

[analogueboy]

Is this something that was recently fixed in 3.2.5? We are currently using 3.2.1 in live, but we are planning to migrate to 3.2.5 in the coming weeks.

TIA