-
Bug
-
Resolution: Done
-
Critical
-
EAP 5.1.0 Post Release, EAP_EWP 5.2.0 ER2
-
None
-
Release Notes
-
-
Documented as Resolved Issue
-
NEW
Two consecutive calls to suspend the deployment scanner via JMX will put the deployment scanner in a state such that resume() no longer functions. All calls to resume act as no-ops.
Error appears to be in HDScanner class.
- is blocked by
-
JBIDE-11215 JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
- Closed
-
JBIDE-12643 Deployment to EAP 5.1 does not work after stopping and starting the deployer using JMX
- Closed
- relates to
-
JBPAPP-9646 Server refuses to pick up hot deployments changes in rare situation
- Closed
-
JBIDE-13013 Deployment scanner in EAP5 works even if stopped via jmx
- Closed