> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 29. lipanj 2002 16:59 > To: Tomcat Developers List > Subject: Re: mod_jk startup > > > > > > 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. >
Agreed. I'll combined it with the 'init' of the jni channel. > > 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. > My reason for that was that we could skip the initialization wait, but you are right, I'll make it default for jni. > Also, why a new jkStatus method instead of setAttribute() ? > Need the static call, cause its called from TomcatStarter, and since I don't need to pass nothing fancy, that was the simplest thing I can think of. MT. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
