Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.3.Final (EAP)
-
None
Description
For the patching service, the patch command leaves the server in a restart-required state
[standalone@localhost:9999 /] patch /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/patch.zip
{
"outcome" : "success",
"response-headers" : {
"operation-requires-restart" : true,
"process-state" : "restart-required"
}
}
If I try to change the AS7 configuration, the CLI warns me that a restart is required, for example:
[standalone@localhost:9999 hornetq-server=default] ./queue=foo:add(queue-address=foo)
{
"outcome" => "success",
"response-headers" => {"process-state" => "restart-required"}
}
However, when I reload the server using the /:reload command, the process-state header is cleared out:
[standalone@localhost:9999 hornetq-server=default] /:reload
{"outcome" => "success"}
[standalone@localhost:9999 hornetq-server=default] ./queue=bar:add(queue-address=bar)
{"outcome" => "success"}
This is not correct: until the server is restarted (not reloaded), the result of my patch operation will not be taken into account (eg changing the AS7 module path).
Reloading the server should not clear its process-state if it is set to "restart-required"
Attachments
Issue Links
- is related to
-
-
- Resolved
-
