[
https://issues.jboss.org/browse/AS7-1384?page=com.atlassian.jira.plugin.s...
]
Jason Greene resolved AS7-1384.
-------------------------------
Assignee: Brian Stansberry
Resolution: Partially Completed
The remaining portion can't be solved in a synchronous call, other ideas are welcome
but in that case would be a feature not a bug.
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
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
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