Hi,
Some more explanations about the recent patch. All the worker initialization checking is done in the load balancer. The only drawback is that all the calls are disabled until the worker finishes with the initialization (perhaps it could be done inside the worker itself but IMO it will be the same). The load balancer has now the additional config parameter 'initTimeout' (default is 1 minute). [lb:lb] info=Default load balancer. disabled=0 debug=0 initTimeout=30 That means that all the calls will be locked until the worker finishes with the initialization or times out. The cost of the init is small for the socket channels (simple connect), but the JNI initialization can take a while. The channel JNI has now new config param 'init' that when set to nonzero waits until the TomcatStarter class calls the jkStatus native method. [channel.jni:jni] info=The jni channel, used if tomcat is started inprocess disabled=0 debug=0 init=1 That will cause to wait until the TC is started, meaning that all the calls to the channel will be blocked. MT. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
