/show_bug.cgi?id=20551
JK2 module for AOLserver
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=20551
JK2 module for AOLserver
--- Additional Comments From [EMAIL PROTECTED] 2003-06-09 22:06 ---
Created an attachment (id=6725)
Updated ant build files
-
To unsubscribe, e-mail: [EMAIL PROTECTED
/show_bug.cgi?id=20551
JK2 module for AOLserver
--- Additional Comments From [EMAIL PROTECTED] 2003-06-09 22:06 ---
Sync'ed ant build files. Archive attached.
Also, following files are no longer needed under
[Apache]/jakarta-tomcat-connectors/jk/native2/server/aolserver and could be
dropped
/show_bug.cgi?id=20551
JK2 module for AOLserver
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Additional Comments From [EMAIL
/show_bug.cgi?id=20551
JK2 module for AOLserver
Summary: JK2 module for AOLserver
Product: Tomcat 4
Version: 4.1.24
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component
/show_bug.cgi?id=20551
JK2 module for AOLserver
--- Additional Comments From [EMAIL PROTECTED] 2003-06-06 16:01 ---
Created an attachment (id=6672)
JK2 connector module for AOLserver 4.0
-
To unsubscribe, e-mail: [EMAIL
Alexander Leyke wrote:
Hi,
A question about enhancement adoption process - how long does it
typically take for new code to show up in CVS, in nightly builds? What
is the verification process for new code? I have posted enhancement
request to the mailing list and to Bugzilla
Alexander Leyke wrote:
Hi,
A question about enhancement adoption process - how long does it
typically take for new code to show up in CVS, in nightly builds? What
is the verification process for new code? I have posted enhancement
request to the mailing list and to Bugzilla
Hi,
A question about enhancement adoption process - how long does it
typically take for new code to show up in CVS, in nightly builds? What
is the verification process for new code? I have posted enhancement
request to the mailing list and to Bugzilla
/show_bug.cgi?id=18283
JK2 module for AOLserver
Summary: JK2 module for AOLserver
Product: Tomcat 4
Version: 4.1.18
Platform: Sun
URL: http://www.mail-archive.com/tomcat-
[EMAIL PROTECTED]/msg41789/nsjk2-4.1.18-src.tar.gz
/show_bug.cgi?id=18283
JK2 module for AOLserver
--- Additional Comments From [EMAIL PROTECTED] 2003-03-24 17:33 ---
Created an attachment (id=5479)
Sources for nsjk2 module
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Hello,
Please find attached archive with sources for nsjk2 module. The module
targets AOLserver 4.0 beta 3 or later. The archive structure is rooted
at jakarta-tomcat-connectors-4.1.18-src, and one can extract files
directly into the JTC-4.1.18 sources. I have successfully built nsjk2 on
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
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
Alexander Leyke wrote:
The JNI channel is special because it is single-threaded ( a doors channel
will use the same type of code ), and that has some implications in
how the request is processed - but the data encoding is the same.
Does it mean that in-process worker is a performance
Costin Manolache wrote:
In jk2, all those strings are eliminated ( from C side ), we also eliminate
the buffer allocation ( we reuse the same jbyteArray and C array, with
code to eventually support NIO - that cuts 2 memcpy and few other small
things ). We also reduce the number of JNI calls to
Alexander Leyke wrote:
You can configure a different starter ( TomcatStarter did work
with an older version of BootstrapService - now you can't use
the 4.1 version of BS without daemon ). You can probably try
to just configure it to use o.a.catalina.startup.Bootstrap.
( or a different starter
Costin Manolache wrote:
I used BootstrapService because it didn't create the 8005 shutdown
socket. My tests were done with 4.0.
You can create your own wrapper, use CatalinaService directly or
call Bootstrap ( if you don't mind 8005 - in your case it doesn't
matter too much since you'll have a
Alexander Leyke wrote:
I used BootstrapService because it didn't create the 8005 shutdown
socket. My tests were done with 4.0.
You can create your own wrapper, use CatalinaService directly or
call Bootstrap ( if you don't mind 8005 - in your case it doesn't
matter too much since you'll have a
Alexander Leyke wrote:
Costin Manolache wrote:
In jk2 we use ajp13 for all channels, including JNI. That allows us to
reuse the buffers and avoid object allocations from C - which improves a
lot the performance of the code ( we also avoid a lot of expensive calls,
etc ). Same technique is also
Thanks for the reply, Costin. There are some more questions below.
Costin Manolache wrote:
Ajp13 protocol ( marshalling, etc ) is used for in-process communication
and out of process communication. By marshalling the data we avoid some
expensive and complex JNI operations, and benefit of all
Hello!
I am working on a JK2 module for AOLserver and would like to receive
feedback on JNI and compiler issues I encountered. My environment is
Solaris 7, AOLserver 3.4 and Tomcat 4.1.12. Issues:
1) Can't use JNI worker. AOLserver follows single-process,
multi-threaded architectural model
Alexander Leyke wrote:
ajp13 worker factory seems to be hardcoded regardless of actual worker
type. Here is a snippet from JTC-4.1.12/jk/native2/common/jk_workerEnv.c:
The reason is simple.
There are 2 interfaces: protocol and channel. In jk1, the JNI used its own
protocol ( using
Costin Manolache wrote:
In jk2 we use ajp13 for all channels, including JNI. That allows us to reuse
the buffers and avoid object allocations from C - which improves a lot the
performance of the code ( we also avoid a lot of expensive calls, etc ).
Same technique is also used (AFAIK) in mozilla
24 matches
Mail list logo
