[jboss-jira] [JBoss JIRA] (AS7-3916) Concurrent access leads to empty domain.xml
[
https://issues.jboss.org/browse/AS7-3916?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3916:
---------------------------------------
The issue likely relates to this log message during boot:
23:19:49,924 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread)
Operation ("add") failed - address: ([("deployment" =>
"********.rar")]) - failure description: "JBAS010858: No deployment content
with hash 638cdd450965166a77fef065e11116ae8e77dff1 is available in the deployment content
repository."
Why the content wasn't in the repository is not clear. The effect of that message
though is the Host Controller did not start cleanly and should have terminated. Since it
didn't terminate, subsequent use of the console or CLI that updated config would lead
to a partial model being written out, which is the cause of the mostly empty domain.xml.
So we're working now to resolve the problem where the HC process didn't terminate
when it couldn't properly process the domain.xml.
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