Re: mod_jk jni worker - apache + number of processes

[Costin Manolache]

The only way to do in-process with apache on unix is to use a 
multithreaded MPM and a small number of processes ( and lots of 
threads). JNI is not much more efficient than IPC - or at least not
in the simplistic use. Even the applets in mozilla/konqueror/etc run out 
of process on unix ( but in-process on win and macosx ).

Writting apache modules in java has been attempted before - 
unfortunately it never quite worked, and the multiprocess issue is just 
one of the problems.

Costin
Fox,Tim wrote:
Hi Mladen -
Thanks for your reply.
I suspected as much.
My real motivation here is to basically provide a java implementation of an 
apache module or filter. I didn't want to communicate via sockets or whatever 
to a shared java process due to performance considerations.
Especially for doing stuff like setting the apache uri or filename via the 
request_rec, I thought that this would incur too much overhead.
I'm guessing this is something that has been considered before. Any ideas? 
Maybe it's already been discounted for these reasons?
Anyway, I guess this is turning into an Apache httpd question rather than a 
tomcat one! :)

-----Original Message-----
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: 18 January 2005 12:43
To: Tomcat Developers List
Subject: Re: mod_jk jni worker - apache + number of processes
Fox,Tim wrote:
Hi All-
Apologies for cross-posting from the user group - but in 
retrospect I believe this might be a better forum for this question:
I am interesting in using the in processes jni_worker with 
apache 2.0 on linux.
My question concerns the number of instances of a jvm, and 
hence tomcat that will be created.
My understanding is that, on linux the default mpm 
configuration will have multiple child server processes created.
Does that mean there will be multiple jvms and hence 
multiple tomcat instances instantiated? Or is the jvm somehow 
"shared" across processes?

You listed all the problems JNI connector faces on Linux, and also the
facts why JNI is unusable.

Is it a requirement of using the jni worker that the number 
of child server processes is limited to 1 in the apache config?
I would suggest that you forgot all about inprocess JNI on any
unix variant with Apache, or better all together.
Even the stupid .NET has a separate process out of IIS.
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]