Bug 900794 (JBEWS-33) - Mod_jk: recover_time is not properly used
Summary: Mod_jk: recover_time is not properly used
Keywords:
Status: CLOSED NOTABUG
Alias: JBEWS-33
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: mod_jk
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Mladen Turk
QA Contact: Jan Stefl
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-16 14:54 UTC by Jan Stefl
Modified: 2014-08-08 04:06 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-14 13:58:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 900723 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker JBEWS-33 0 Minor Closed Mod_jk: recover_time is not properly used 2014-08-14 08:24:33 UTC

Internal Links: 900723

Description Jan Stefl 2012-08-16 14:54:24 UTC
Affects: Release Notes
Workaround Description: A workaround could be to set the worker.maintain interval to the desired recover_time asw well.
project_key: JBEWS

The recover_time applies correctly the first time, but only the first time.

Please see:
https://issues.apache.org/bugzilla/show_bug.cgi?id=52334

Comment 1 Jan Stefl 2012-08-16 14:54:42 UTC
Link: Added: This issue relates to JBPAPP-9551


Comment 2 David Knox 2012-09-12 22:58:00 UTC
Reassigning to Weinan. I believe this is a mod_jk issue.

Comment 3 Weinan Li 2012-09-19 07:35:44 UTC
I'm working on this one.

Comment 4 Weinan Li 2012-09-19 15:28:16 UTC
Hi Jan,

I've just read the upstream bug report. So let's patch this after upstream release a fix for this.

Comment 5 Jan Stefl 2012-09-19 15:36:33 UTC
Hi Weinan,
ok understand, we will wait. Thanks for the info.

Comment 6 Permaine Cheung 2012-10-04 13:49:11 UTC
As this is an upstream issue, we should wait for the fix in a future release and inherit that fix in EWS when we update to the new version.

Comment 7 Libor Fuka 2012-10-17 12:06:13 UTC
Release Notes Docs Status: Added: Not Yet Documented
Affects: Added: Release Notes


Comment 8 Jan Stefl 2012-10-17 16:45:44 UTC
Release Notes Text: Added: The recover_time applies correctly the first time, but only the first time.  This becomes evident when setting recover_time larger than 60 seconds and larger than worker.maintain.  After the first recover attempt passes and the worker errors back out to its global error state, the worker will be placed in recovery mode again on the next invocation of the worker.maintain method.
Workaround Description: Added: A workaround could be to set the worker.maintain interval to the desired recover_time asw well.


Comment 9 Misha H. Ali 2012-10-24 04:10:11 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue
Writer: Added: mhusnain
Release Notes Text: Removed: The recover_time applies correctly the first time, but only the first time.  This becomes evident when setting recover_time larger than 60 seconds and larger than worker.maintain.  After the first recover attempt passes and the worker errors back out to its global error state, the worker will be placed in recovery mode again on the next invocation of the worker.maintain method. Added: The recover_time value is only applied correctly once (the first time). The problem manifests when recover_time is set to a value greater than 60 seconds and is greater than the value of worker.maintain. After the first recover attempt passes and the worker errors back out to its global error state, the worker will be placed in recovery mode again on the next invocation of the worker.maintain method.


Comment 10 Jiri Skrabal 2012-11-13 15:56:35 UTC
Release Notes Docs Status: Removed: Documented as Known Issue 
Writer: Removed: mhusnain 
Release Notes Text: Removed: The recover_time value is only applied correctly once (the first time). The problem manifests when recover_time is set to a value greater than 60 seconds and is greater than the value of worker.maintain. After the first recover attempt passes and the worker errors back out to its global error state, the worker will be placed in recovery mode again on the next invocation of the worker.maintain method. 
Docs QE Status: Removed: NEW 


Comment 11 Jean-frederic Clere 2013-05-08 14:06:08 UTC
No fix upstream for the moment: https://issues.apache.org/bugzilla/show_bug.cgi?id=52334


Note You need to log in before you can comment on or make changes to this bug.