Bug 900794 (JBEWS-33)

Summary:	Mod_jk: recover_time is not properly used
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Jan Stefl <jstefl>
Component:	mod_jk	Assignee:	Mladen Turk <mturk>
Status:	CLOSED NOTABUG	QA Contact:	Jan Stefl <jstefl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0.0	CC:	dknox, jclere, jstefl, lfuka, mhasko, mhusnain, myarboro, pcheung, pslavice, rsvoboda, weli
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEWS-33
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The <parameter>recover_time</parameter> value is only applied correctly once (the first time). The problem manifests when <parameter>recover_time</parameter> is set to a value greater than <literal>60</literal> seconds and is greater than the value of <parameter>worker.maintain</parameter>. After the first recovery attempt concludes and the worker errors return to the global error state, the worker is placed in recovery mode again on the next invocation of the <parameter>worker.maintain</parameter> method. This is a known issue in JBoss Enterprise Web Server 2.0.1 and currently no workaround is available for this issue.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-14 13:58:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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