[
https://issues.jboss.org/browse/AS7-3916?page=com.atlassian.jira.plugin.s...
]
William Bendrot commented on AS7-3916:
--------------------------------------
Trying to recreate on a clean domain cluster today and so far unable to recreate. Will
keep trying. But we did uncover the error that was reported in the console when the
problem had manifested:
Unexpected HTTP response: 500
Request
{
"operation" => "read-resource",
"address" => [("server-group" =>
"server-qa-server-group")],
"recursive" => true,
"include-runtime" => true
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource
'[(\"server-group\" => \"server-qa-server-group\")]' not
found",
"rolled-back" => true }
Also a sign that it was about to occur was the server logs would stop populating during
restart. We are contiuning testing this week and will report back results.
Concurrent access leads to empty domain.xml
-------------------------------------------
Key: AS7-3916
URL:
https://issues.jboss.org/browse/AS7-3916
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Labels: eap6_LA
Fix For: 7.1.1.Final
Attachments: DomainXML.jmx.zip
Hi Red Hat team. We're still trying to narrow down the trigger but there is a very
serious bug when using the admin console in AS 7.1 Final that causes the domain.xml file
to be wiped of everything other than the extensions section that is at the top. Have not
checked yet if this is a known bug or not but wanted to alert you immediately.
The potential trigger for this is more than one person using the admin
console at the same time. Even if just for monitoring while the other
person is making configuration changes. (Fortunately we had backed up
the config using the CLI.)
We are trying right now to get our QA1 drop out the door but we'll be
giving this a closer look tomorrow. Has anyone else reported this though?
Thanks,
Bill
--
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