Bug 879065 - [jboss-as5] Shutdown max wait time "shared" between different resources
Summary: [jboss-as5] Shutdown max wait time "shared" between different resources
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: ---
: RHQ 4.9
Assignee: Thomas Segismont
QA Contact: Mike Foley
: 879066 (view as bug list)
Depends On:
Blocks: 846362
TreeView+ depends on / blocked
Reported: 2012-11-22 00:12 UTC by Larry O'Leary
Modified: 2014-03-26 08:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 846362
Last Closed: 2014-03-26 08:31:13 UTC

Attachments (Terms of Use)

Description Larry O'Leary 2012-11-22 00:12:44 UTC
+++ This bug was initially created as a clone of Bug #846362 +++

Created attachment 602782 [details]
proposed patch

Description of problem:
This is a concurrency issue.

The problem is that while a shutdown operation on some AS5 resource is in progress, executing the shutdown operation on another AS5 resource on the same agent will override the max wait time of the two operations to the same value defined by the latter resource.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. have 2 AS5 resources in inventory, make sure their shutdown takes more than 1 minute (not sure how to do this actually - possibly install a custom MBean that implements MBeanRegistration interface and sleep in preDeregister()?)
2. set the max wait time of 1 to 15 minutes, and 1minute on the other (2).
3. run shutdown on 1.
4. immediatelly run shutdown on 2
Actual results:
The operation on the server 1 times out after 1 minute

Expected results:
The operation on the server 1 should only timeout after 15 minutes or complete normally.

Additional info:

--- Additional comment from mark yarborough on 2012-11-20 15:45:46 EST ---

Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).

Comment 1 Thomas Segismont 2013-08-14 13:21:28 UTC
*** Bug 879066 has been marked as a duplicate of this bug. ***

Comment 2 Thomas Segismont 2013-08-14 14:54:10 UTC
Fixed in master (see BZ846362)

commit 2a21d7b3a9a97248df2ab6d9d83804663c55972b
Author: Thomas Segismont <tsegismo@redhat.com>
Date:   Wed Aug 14 16:51:00 2013 +0200

Comment 3 Heiko W. Rupp 2014-03-26 08:31:13 UTC
Bulk closing now that 4.10 is out.

If you think an issue is not resolved, please open a new BZ and link to the existing one.

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