> -----Original Message----- > From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]] > Sent: 28. lipanj 2002 1:28 > To: 'tomcat-dev' > Subject: [JK2] JNI worker Init complete > > > When tomcat is started inprocess ( by JNI ) we need a way to > signal when tomcat ( 3.3 and 4.1.X ) initialization is > complete, and make jk2 wait until that signal to start > redirecting request to the JNI worker.. >
I have the same problems, (I've posted that on Monday)... The problem is also with the channel itself, cause the first invocation of channel.open takes some time, but I solved that cause there was the multithreading bug in the code. > I think i will need too another kind of invoke message, to > signal inited state from tomcat, from Coyote/JK2.., any help > is welcomed.. > There is no need to do that for initialization. All that we require is the worker startup flag, with the timeout probably. Second large improvement would be (think you meant that) the introduction of a special fixed single 'maintenance' channel, that could be used for server<->TC communication, sending status and control messages like restart/shutdown/busy/resource, etc... Running as a separate thread (or something like that) for each TC-channel combination in the load balancer. I'm pretty close to the first solution (disabling all communication until the first worker call succeeds, in the preset timeout), and I'll post it for review when I thoroughly test it. MT. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
