Alexander Leyke wrote: > > > Costin Manolache wrote: > >>Are you using the jni channel ? Is that working too ? >> >> > No, it is the default ajp13 channel. I think I told you about my doubts > about jk_workerEnv.c hardcoding "ajp13" as the type for all channel > initialization. Anyway, this is how the code looks like now (let me know > if I am missing the point here). Would the code I have commented out use > jni channel?
I don't think so. AFAIK jni uses the ajp13 protocol over jni channel. All you have to do is define the config: In workers2.properties: [channel.jni:jni] info=The jni channel, used if tomcat is started inprocess debug=10 [worker.jni:jniCmd1] info=Command to be executed by the VM. This one will start tomcat. class=org/apache/jk/apr/TomcatStarter ARG=start debug=10 [uri:/... ] worker=jni The moment you define the channel.jni stuff it'll create automatically a worker with the same name, and you can map to that worker. ( the worker will be of ajp13 type - but use the jni channel ). ( yes, I know - we need more documentation ). >>Regarding jsp - it uses ant to compile, so you may want to set a >>system property to specify the compiler ( you can do it in the worker >>config ). I use "build.compiler=jikes" :-) >> >> > Not sure how the things are related to ant. Standalone Tomcat compiles > JSP perfectly well, so I think this is related to runtime environment, > some option missing from in-process environment. Isn't ant used strictly > at build time, and JSP compile done by Tomcat translating things to Java > and then calling JVM to compile into bytecode? Tomcat4.1 uses javac task from ant to compile. ( no build file - it embeds it ). That means any settings from ant would work. ( ant is pretty good at compiling - the idea was to avoid duplicating this ). > I think there is a 4th phase, shutdown. What does servlet spec say about > shutdown, is there a way to register a "shutdown" servlet - loosing that > capability may not be the best thing. I do see slightly different > behavior now - there is a "Service shutting down" message from Tomcat, > but AOLserver shutdown messages are missing. It could be bugs in my > code, I know I forgot to initialize JVM in separate thread (has to do > with AOLserver disabling signals in main thread, and JVM depending on > them to do garbage collection). Tomcat registeres a shutdown hook ( with JDK1.3+ I think ). I think Mladen added shutdown hooks - but I never tested this. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
