On Sat, 29 Jun 2002, Mladen Turk wrote: > All the worker initialization checking is done in the load balancer.
+1 ! ( can I say "I was thinking the same" ? ) > The load balancer has now the additional config parameter 'initTimeout' > (default is 1 minute). > > That means that all the calls will be locked until the worker finishes > with the initialization or times out. Not sure about that. It's probably ok, but I think initTimeout should be a property of the channel ( and maybe only of the JNI channel, since socket will connect and reconnect several times ), and only that worker should wait. We can change this later, is not a big problem. > The channel JNI has now new config param 'init' that when set to nonzero > waits until the TomcatStarter class calls the jkStatus native method. Does it have to be an option ? jk1 did wait in all cases, and I don't see any reason to set 'init' to 0. Also, why a new jkStatus method instead of setAttribute() ? Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
