From: <Dom...@vo...> - 2004-12-22 12:40:12
|
Hi all, we are using Jetty with AJP13 and HTTP connectors where the AJP13 = connects to the frontend and will do the 'normal' work and the http = connector is just for internal use (to connect direct to the jettys to = see status pages etc.).=20 Now we observed the following behaviour of the jetty server during = startup: -> jetty is coming up and starts the AJP13 connectors -> jetty initializes and starts the webapps -> jetty starts http connectors The question is:=20 Why are the AJP13 connectors started before the webapps are initialized? = The behaviour of the http-connector makes more sence from our point of = view. The problem is that the software loadbalancer will start sending = requests to the jetty until the AJP13 connector is available and those = requests cannot be handled until the webapps are up and running.=20 Is there a possibility to change this behaviour? I haven't found = anything in the docs.=20 Thanks for any help or comments, I can provide additionial information, = if required. Best regards Dominik Helleberg |