With worker - it may work. However you may find mod_jk inprocess to be
slower than ajp and mod_proxy ( or comparable in speed ), this is due to
the way parameters are passed as strings ( i.e. lots of unoptimized
char-byte conversion ).
Porting to 5.5.x shouldn't be hard - the interface between tomcat and
modjk is very simple: you need to startup, i.e. make sure classpath is
set and the class that executes launches tomcat correctly, and then it's
a simple class that does the request/response passing.
If you do this for performance reasons - you may want to look at the
code in jk2, and try to backport it. A benefit would be that the
interface is even simpler - the req/response are passed in the same kind
of buffer as ajp requests. AFAIK that's the only major difference. Since
Remy, Mladen, etc have greatly optimized the regular tcp connectors -
probably the difference on performance ( with this optimization
backported ) will be small. But if you use the old style of interface -
I'm sure jni will be slower (it was slower 2 years ago).
Costin
Christine Ho wrote:
Hi,
Thanks a lot. I am really appreciated for your
reply. How about the worker MPM? My team is running
the httpd.worker on RHEL4. The current setting is:
StartServers 1
ServerLimit 1
MaxClients 64
MinSpareThreads 32
MaxSpareThreads 64
ThreadsPerChild 64
Does the inprocess Tomcat 5.5.9 work for the worker
MPM?
thanks,
Christine
--- Bill Barker <[EMAIL PROTECTED]> wrote:
Well, inprocess doesn't really work for any MPM on
*nix systems (e.g. with
the prefork MPM, you end up with MaxChild copies of
Tomcat running :). As a
result, there just hasn't been that much interest in
implementing (or even
back-porting) a feature that only works on Windows
and NetWare.
----- Original Message -----
From: "Christine Ho" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 16, 2005 3:30 PM
Subject: inprocess Tomcat/apache via mod_jk
Hi,
I have posted this email a month ago. I just
wonder
if any developer on mod_jk can answer my question. I
would like to have inprocess Tomcat 5.5.9 running in
Apache 2.x if possible.
thanks again,
Christine
Hi,
I tried to setup Tomcat 5.5.9 running inside the
apache server 2.x via the mod_jk on RHEL4. I got the
following error:
[debug] open_jvm2::jk_jni_worker.c (1055): JVM
created
[emerg] get_bridge_object::jk_jni_worker.c (1097):
Can't find class
org/apache/tomcat/modules/server/JNIEndpoint
I looked at the mod_jk source codes and found out
that
the mod_jk supports the TC32_BRIDGE_TYPE and
TC33_BRIDGE_TYPE. It doesnt support bridge type of
tomcat 4.x and up. Plus the tomcat 5.5.9 doesnt have
the JNIEndpoint.class.
However, it seems to me that the deprecated mod_jk2
supports bridge type of tomcat 4.x and up because it
tries to instantiate the class
org/apache/jk/apr/TomcatStarter.class which exists
in
tomcat-ajp.jar.
I really dont understand why the mod_jk supports
tomcat 3.x only whereas the deprecated mod_jk2
supports tomcat 4.x and 5.x. Can somebody please
tell
me why?
Also is it easy to have mod_jk to support
TC55_BRIDGE_TYPE? Based on the mod_jk source codes
jk_jni_worker.c, I think I just need to define the
TC55_JAVA_BRIDGE_CLASS_NAME to be
org/apache/jk/apr/TomcatStarter.class and then
assign
it to the btype. Is it just that simple?
Another question is what the disadvantages of
running
tomcat inside the apache are. I googled and it seems
to me that not too many people try to run inprocess
tomcat inside apache. I would be interested in
adding
the 5.5 bridge type to the mod_jk.
thanks,
Christine
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
This message is intended only for the use of the
person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and
CONFIDENTIAL. If you are not an intended recipient,
you may not read, copy, or distribute this message
or any attachment. If you received this
communication in error, please notify us immediately
by e-mail and then delete all copies of this message
and any attachments.
In addition you should be aware that ordinary
(unencrypted) e-mail sent through the Internet is
not secure. Do not send confidential or sensitive
information, such as social security numbers,
account numbers, personal identification numbers and
passwords, to us via ordinary (unencrypted) e-mail.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
