[jboss-jira] [JBoss JIRA] (AS7-1384) Strange state after :reload
[
https://issues.jboss.org/browse/AS7-1384?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1384:
---------------------------------------
This should be fixed now except for the "{"result" => } should be
defined and not just null" part.
The tricky part with all this is the response has to be sent before the reload actually
gets going (since the reload will break the connection to the client). So all the response
can be is an indication of what the server tried to do, not what happened.
A high level command on the CLI could be smarter; i.e. client side logic in the CLI could
poll the server to see if it comes up.
Strange state after :reload
---------------------------
Key: AS7-1384
URL: https://issues.jboss.org/browse/AS7-1384
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Final
Reporter: Heiko Rupp
Fix For: 7.1.0.Beta1
7.1 snapshot
I did change a socket binding, so reload is needed. Did a /:read-resource
Then :reload
},
"response-headers" => {"process-state" =>
"reload-required"}
}
[standalone@localhost:9999 /] :reload
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9999 /] :reload
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
I think after the reload (which succeeded) the process-state should no longer be
"reload needed".
Also
{"result" => } should be defined and not just null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira