DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34549.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34549.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34549.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-jk-native has an issue affecting its community
integration.
This
Hi,
Those 2 are reported against Daemon, but the user is looking for a safe way to
know that Tomcat is completly up (AJP connector ready) or completly down. In
jsvc the completly down case is easy: the JVM has exited.
Any hints for the completly up case?
Cheers
Jean-frederic
Many way :
- check the AJP port is listening on the right port.
- Add a 'status' file in AJP support created after AJP is completly up
and destroyed when AJP is closing.
BTW, it will be better to have such file created when Tomcat is fully
started (independant from AJP which could be
mturk 2005/04/21 03:36:58
Modified:jk/native/common jk_map.c jk_util.c jk_util.h
Log:
Add is_unique property check, so that multiple unique directives override
each other, instead making a list out of unique property values.
Increase the read buffer size to 8K, that should be
mturk 2005/04/21 04:18:44
Modified:jk/native/common jk_ajp_common.c jk_global.h jk_lb_worker.c
Log:
Make sure the returned status codes are the same for ajp and lb
workers.
Status 503 if connection to tomcat fails.
Status 502 is returned if tomcat faild in the middle of
mturk 2005/04/21 04:36:29
Modified:jk/native/common jk_ajp_common.c jk_connect.c jk_connect.h
Log:
Remove unused timeout parameter for testing if socket is connected.
Revision ChangesPath
1.98 +3 -3
jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
mturk 2005/04/21 04:41:06
Modified:jk/native/common jk_ajp_common.c
Log:
Fix bug in check next connection loop, by resetting test value to 0
for each socket.
Revision ChangesPath
1.99 +3 -2
jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
mturk 2005/04/21 04:51:07
Modified:jk/native/common jk_ajp_common.c
Log:
Close the socket only if the lock can be obtained.
Revision ChangesPath
1.100 +5 -4
jakarta-tomcat-connectors/jk/native/common/jk_ajp_common.c
Index: jk_ajp_common.c
mturk 2005/04/21 05:04:02
Modified:jk/native/common jk_ajp14.c
Log:
Make jk_msg_buf_t structure public to skip the need for calling functions
for accessing structure elements.
Revision ChangesPath
1.27 +3 -3
mturk 2005/04/21 05:04:18
Modified:jk/native/common jk_ajp_common.c jk_msg_buff.c jk_msg_buff.h
Log:
Make jk_msg_buf_t structure public to skip the need for calling functions
for accessing structure elements.
Revision ChangesPath
1.101 +16 -16
mturk 2005/04/21 05:14:21
Modified:jk/native/common jk_msg_buff.c
Log:
Dump entire message if log level is trace. In debug level log first 1024
bytes.
Revision ChangesPath
1.30 +2 -8 jakarta-tomcat-connectors/jk/native/common/jk_msg_buff.c
Index:
keith 2005/04/21 06:01:45
Modified:catalina/src/share/org/apache/catalina/authenticator Tag:
TOMCAT_5_0 AuthenticatorBase.java
Log:
[34083, 27122, 28662, 29336, 29975, and 30618]
Back out my previous change at Remy's wish so now Tomcat 5.0 too
is
No one has commented so I withdraw my (valid) veto and I'll roll back
5.0 per Remy's wish. I'm disappointed because I remember when Tomcat
was an open-source project.
Keith
My veto of this change still stands, and it would be your responsibility
of finding a fix more compatible with IE. If no
Hi,
Here are the brief results for Tomcat HEAD:
Server Threads Pause (ms) Error(%) Rate (req/sec)
Apache2.0.49500 1000 1.74 124.2
Http11Protocol 500 1000 0.20 139.5
Http11AprProtocol 500 1000 0.00 266.9
Tests has been run on
Cool. I assume you were finally able to my test plan mladen? I plan
to run the benchmarks on my system this weekend, not that my laptop is
healthy.
peter
On 4/21/05, Mladen Turk [EMAIL PROTECTED] wrote:
Hi,
Here are the brief results for Tomcat HEAD:
Server Threads Pause (ms)
Peter Lin wrote:
Cool. I assume you were finally able to my test plan mladen?
Yes. I've run them extensively, thanks for sharing those.
Been playing with the constant timer, number of threads, etc...
Results show that for high number of connections the APR
implementation is way ahead of any other.
I'll be using my AMD 2ghz linux box running Fedora Core1. haven't
updated to FC3 yet, though remy keeps suggesting I upgrade :)
peter
On 4/21/05, Mladen Turk [EMAIL PROTECTED] wrote:
Peter Lin wrote:
Cool. I assume you were finally able to my test plan mladen?
Yes. I've run them
Would we expect anything markedly different with Apache 2 worker rather
than prefork? This would seem a bit more of an apples-to-apples
comparison (i.e. comparing multi-threaded low-process count servers).
Also how many simultaneous workers (threads/processes/whatever) were
allowewd in each
Jess Holle wrote:
Would we expect anything markedly different with Apache 2 worker rather
than prefork?
No.
Also I found that the majority of users is usig prefork because of PHP.
This would seem a bit more of an apples-to-apples
comparison (i.e. comparing multi-threaded low-process count
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Henri Gomez wrote:
Many way :
- check the AJP port is listening on the right port.
- Add a 'status' file in AJP support created after AJP is completly up
and destroyed when AJP is closing.
BTW, it will be better to have such file created when Tomcat is fully
started (independant from AJP which
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34526.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33106.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34558.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33106.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
I know that but if your starter wrapper check if the process whom pid
is stored on the file is still alive it could determine if the process
has been aborted via kill -9.
I'm using this kind of hack in Linux init.d rc for at least 2 years,
whitout problems
2005/4/21, Ian F. Darwin [EMAIL
Henri Gomez wrote:
I know that but if your starter wrapper check if the process whom pid
is stored on the file is still alive it could determine if the process
has been aborted via kill -9.
I'm using this kind of hack in Linux init.d rc for at least 2 years,
whitout problems
Right, if you read
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34560.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34561.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
35 matches
Mail list logo
