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=33510>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33510





------- Additional Comments From [EMAIL PROTECTED]  2005-02-12 00:01 -------
apache 1.3.28
mod_jk 1.2.8
tomcat 5.1.30

The two numbers I am referring to are the last two numbers on the logged line 
(42 < 3600).  They are the time elapsed since the worker was determined to be 
in error, and the configured time in seconds before the worker is available to 
connect again.  I've set it to 3600 here (an hour).

The first number should be incrementing by one per second, and you can see in 
the first two logged lines it does.  However, when the minute rolls over on the 
third line, you can see that the elapsed time jumps from 43 to 2475.  I am 
assuming this is because the implementation of the time_t type that I compiled 
with does not simply just contain the number of seconds from an epoch.  Reading 
a little on this I found that you are supposed to use the function difftime() 
in time.h to get an elapsed time value, instead of just subtracting two time_t 
values.  The latter method is used on line 297 of jk_lb_worker.c, and this 
produces unexpected results.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to