[
https://issues.jboss.org/browse/WFCORE-2145?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-2145:
-------------------------------------
Description:
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 correct_
- -During 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}}.
was:
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.
- During a stop, it is even more confusing, because it goes through one extra state -
{{suspending}} which doesn't occur during start.
- The state to represent a suspended server is named {{stopped}} and not {{suspended}}.
Confusing transitions of ControlledProcessState
-----------------------------------------------
Key: WFCORE-2145
URL:
https://issues.jboss.org/browse/WFCORE-2145
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha16
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
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 correct_
- -During 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}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)