Thanks Kabir.
By the way, is there a reason why the attribute is named server-state
and the response header is named process-state?
-Jaikiran
On Friday 04 May 2012 04:37 PM, Kabir Khan wrote:
:read-resource(include-runtime=true) and look for
'server-state'
OR
:read-attribute(name=server-state)
The state is also returned in the response-headers once it goes into the reload-required
state:
[standalone@localhost:9999 /] :read-attribute(name=server-state)
{
"outcome" => "success",
"result" => "reload-required",
"response-headers" => {"process-state" =>
"reload-required"}<<<<<<<<<<
}
On 4 May 2012, at 11:36, Jaikiran Pai wrote:
> Is there a command/operation in the management API which shows me the
> current server process status. For example, I trigger an operation which
> results in a "reload-required" process state:
>
> [standalone@localhost:9999 /]
>
/subsystem=ejb3/service=remote/channel-creation-options=MAX_OUTBOUND_MESSAGES:add(type=remoting,
> value=123)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
>
> Assume some admin decides to do the :reload operation at some later
> point in time and closes his session. At a later point in time, is there
> some way he can get to the process state to verify that a reload is
> required before actually doing a :reload?
>
> -Jaikiran
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev