Red Hat Bugzilla – Bug 879065
[jboss-as5] Shutdown max wait time "shared" between different resources
Last modified: 2014-03-26 04:31:13 EDT
+++ This bug was initially created as a clone of Bug #846362 +++
Created attachment 602782 [details]
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):
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
The operation on the server 1 times out after 1 minute
The operation on the server 1 should only timeout after 15 minutes or complete normally.
--- 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).
*** Bug 879066 has been marked as a duplicate of this bug. ***
Fixed in master (see BZ846362)
Author: Thomas Segismont <email@example.com>
Date: Wed Aug 14 16:51:00 2013 +0200
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.