-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR9
-
None
-
-
-
-
-
-
Not Required
Starting a server into normal mode emits these transitions for the process running state:
- starting -> suspended -> normal
Similarly when transitioning to admin-only mode:
- starting -> suspended -> admin-only
Stopping from normal mode:
- normal -> suspending -> suspended -> stopping
Starting into suspended mode emits:
- starting -> stopping -> stopped
(and the stopped state represents that the server is actually in suspended mode)
I find it confusing that:
During a normal start, it transitions through a state named suspended even though the server is not suspended.this is actually correctDuring a stop, it is even more confusing, because it goes through one extra state - suspending which doesn't occur during start.- this is actually correct- The state to represent a suspended server is named stopped and not suspended.
- is cloned by
-
WFCORE-2145 Confusing transitions of ControlledProcessState
- Resolved
- is incorporated by
-
JBEAP-8294 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta2
- Closed