3:06 p.m.
This is an older issue that I looked at last week. The fix is mostly
trivial, but the associated naming wasn't obvious.
https://issues.jboss.org/browse/WFCORE-43
As a result of the discussion, we're leaning towards:
runtime-configuration-state: {STARTING, OK, STOPPING, RELOAD_REQUIRED,
RESTART_REQUIRED}
host-state and server-state will be preserved for compatability, with the
new OK state mapped back to RUNNING.
Thoughts / comments?
Ken
5:49 p.m.
Shouldn't there be a STOPPED state too for domain servers? Also should it
include SUSPENDING, SUSPENDED and RESUMING as well?
On Mon, Mar 28, 2016 at 12:06 PM, Ken Wills <ken(a)zaptillion.net> wrote:
This is an older issue that I looked at last week. The fix is mostly
trivial, but the associated naming wasn't obvious.
https://issues.jboss.org/browse/WFCORE-43
As a result of the discussion, we're leaning towards:
runtime-configuration-state: {STARTING, OK, STOPPING, RELOAD_REQUIRED,
RESTART_REQUIRED}
host-state and server-state will be preserved for compatability, with the
new OK state mapped back to RUNNING.
Thoughts / comments?
Ken
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
JBoss by Red Hat
9:39 p.m.
On 3/28/16 4:49 PM, James Perkins wrote:
Shouldn't there be a STOPPED state too for domain servers?
Yes, good point. The
org.jboss.as.host.controller.resources.StoppedServerResource will need
to handle this runtime-configuration-state attribute the same way it
handles server-state.
Also should
it include SUSPENDING, SUSPENDED and RESUMING as well?
No, that's a separate attribute because it's reporting on a different
thing. See discussion leading up to
http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html
On Mon, Mar 28, 2016 at 12:06 PM, Ken Wills <ken(a)zaptillion.net
<mailto:ken@zaptillion.net>> wrote:
This is an older issue that I looked at last week. The fix is mostly
trivial, but the associated naming wasn't obvious.
https://issues.jboss.org/browse/WFCORE-43
As a result of the discussion, we're leaning towards:
runtime-configuration-state: {STARTING, OK, STOPPING,
RELOAD_REQUIRED, RESTART_REQUIRED}
host-state and server-state will be preserved for compatability,
with the new OK state mapped back to RUNNING.
Thoughts / comments?
Ken
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
3:14 a.m.
Looks good.
On 28 Mar 2016, at 21:06, Ken Wills <ken(a)zaptillion.net>
wrote:
This is an older issue that I looked at last week. The fix is mostly trivial, but the
associated naming wasn't obvious.
https://issues.jboss.org/browse/WFCORE-43
<https://issues.jboss.org/browse/WFCORE-43>
As a result of the discussion, we're leaning towards:
runtime-configuration-state: {STARTING, OK, STOPPING, RELOAD_REQUIRED, RESTART_REQUIRED}
host-state and server-state will be preserved for compatability, with the new OK state
mapped back to RUNNING.
Thoughts / comments?
Ken
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2948
days inactive
2949
days old
3 comments
4 participants
participants (4)
-
Brian Stansberry -
Heiko Braun -
James Perkins -
Ken Wills