[jboss-jira] [JBoss JIRA] (AS7-4551) Force container to settle before returning from rollback management ops

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-4551:
----------------------------------

    Fix Version/s: 7.3.0.Alpha1
                       (was: 7.2.0.Alpha1)


Moving to 7.3. Looking at the code, the container should be forced to settle. This may not be an issue; there were some intermittent failures in some of the controller module unit tests that have been fixed and may have been what led to this issue.
                
> Force container to settle before returning from rollback management ops
> -----------------------------------------------------------------------
>
>                 Key: AS7-4551
>                 URL: https://issues.jboss.org/browse/AS7-4551
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 7.3.0.Alpha1
>
>
> When an operation fails and triggers rollback, the service container gets modified on the return path of the operation. But the operation does not wait for the container to settle before returning.  This is the source of intermittent failures in org.jboss.as.controller.ModelControllerImplUnitTestCase.testRemoveDependentService -- the test checks container state that may not yet be settled.
> This task is to investigate forcing the container state to settle before releasing the controller lock.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira