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
Good morning,
AFAICT this is working fine with a socket timeout of 15. Neither
/server-info/ or /status/ show the setting in use, but 15 is what's in
the properties file and /server-info/ says that's the file in use.
Regards,
Norm
Mladen Turk wrote:
NormW wrote:
Good evening,
Can confirm a clean
Hi again...
Mladen Turk wrote:
NormW wrote:
Good evening,
Can confirm a clean build for 2.1 and 2.0.53 Apache. Time is short now
but will test them for basic ops in the morning. I assume these still
need the socket_timeout at zero?
Well, new is_socket_connected implementation should be available
NormW wrote:
Good evening,
Can confirm a clean build for 2.1 and 2.0.53 Apache. Time is short now
but will test them for basic ops in the morning. I assume these still
need the socket_timeout at zero?
Well, new is_socket_connected implementation should be available
for netware too (that was the p
Good evening,
Can confirm a clean build for 2.1 and 2.0.53 Apache. Time is short now
but will test them for basic ops in the morning. I assume these still
need the socket_timeout at zero?
Regards,
Norm
-
To unsubscribe, e-mail:
Greetings,
Will see... :-)
N.
[EMAIL PROTECTED] wrote:
mturk 2005/02/19 01:13:35
Modified:jk/native/common jk_ajp_common.c jk_connect.c
Log:
Use alternative is_socket_connected implementation using
select with 1 microsecond timeout. It should be both faster and
usable on netware
mturk 2005/02/19 01:13:35
Modified:jk/native/common jk_ajp_common.c jk_connect.c
Log:
Use alternative is_socket_connected implementation using
select with 1 microsecond timeout. It should be both faster and
usable on netware too.
Revision ChangesPath
1.91 +7 -9
Glenn Nielsen wrote:
> Costin,
>
> Why were the log levels changed from LOG_ERROR to LOG_INFO, a connection
> failure to tomct is a real fatal error when handling a request. Shouldn't
> it be at the JK_LOG_ERROR level?
It'll be logged at ERROR level -
>> +jk_log(l, JK_LOG_ERROR, "Err
costin 2002/10/30 14:12:20
Modified:jk/native/common jk_ajp_common.c jk_connect.c
Log:
More trimming for error messages.
Now only one line ( and hopefully more informative ) is displayed if
we can't send the request to tomcat.
Revision ChangesPath
1.32 +11 -5
