Lenny,
disclaimer: I don't use JSP's myself so I might be totally off here...
but there is the following comment in Tomcat 4.1 Release Notes:
--
Using Jasper 1 with Tomcat 4.1:
--
It is possible to use Jasper 1 (included in Tomcat 4.0.x)
Pier,
I have a releated question - does it also mean that currently mod_webapp
will not work with Apache 2 that uses worker mpm?
thanks
Julius Gawlas
-Original Message-
From: Pier Fumagalli [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 07, 2002 9:57 AM
To: Tomcat Developers
Hi,
I wanted to build jk2, but I could not find neither configure nor
makefiles in jk/native2.
Could you give me some pointers?
thanks
Julius
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
I am reposting that patch again - let me know if there are any questions or
concerns.
Seems like the latest j-t-c mod_jk calls initialization (init_jk) twice -
once during post_config and then in child_init. This has a side effect of
trying to create non existing workers and subsequently
Seems like the latest j-t-c mod_jk calls initialization (init_jk) twice -
once during post_config and then in child_init. This has a side effect of
trying to create non existing workers and subsequently failing. Enclosed
simple patch prevents second initialization call.
Julius
Index: mod_jk.c
I am trying to make inprocess tomcat work with Apache 2.0 without much
success.
I am using j-t-c mod_jk from cvs. First I noticed that since Apache calls
module initialization twice jni worker fails when trying to load jvm the
second time.
I found in the archives that that issue has been
Costin,
The main problem with JNI and apache is that we can't support sessions
corectly. Apache is a multi-process server ( even apache2.0 -
each process
has multiple threads, but it's still multiprocess ).
Thanks for quick answer, but I don't think I can quite see
contradiction here - I
Costin,
With JNI, each apache process will have it's own VM and will process
requests. If a session is created, it'll be in one of the VMs,
and the servlet spec requires that all further requets within that
session go to the same VM.
This is not possible right now - a second request can
This patch contains minor fixes for mod_jk for Apache 2.0;
Most important is the change in prototype of jk_post_config
which used to be void but now needs to return success code,
also changes to types of some variables to better confirm to
Apache 2.0 types.
Let me know if you have any
