[jboss-jira] [JBoss JIRA] (AS7-5658) Deadlock when using ConfigAdmin from within a mgmnt op

Tue Oct 2 05:45:03 EDT 2012

    [ https://issues.jboss.org/browse/AS7-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723184#comment-12723184 ] 

Thomas Diesler commented on AS7-5658:
-------------------------------------

{code}
Running org.jboss.as.test.integration.osgi.configadmin.ConfigAdminServiceTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.037 sec
Running org.jboss.as.test.integration.osgi.configadmin.ConfigAdminIntegrationTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.016 sec
Running org.jboss.as.test.integration.osgi.configadmin.ConfigurationAdminTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.67 sec
{code}
                
> Deadlock when using ConfigAdmin from within a mgmnt op
> ------------------------------------------------------
>
>                 Key: AS7-5658
>                 URL: https://issues.jboss.org/browse/AS7-5658
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: ConfigAdmin
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>            Priority: Critical
>             Fix For: 7.2.0.Alpha1
>
>
> Nested mgmnt ops deadlock. This could easily happen when ConfigAdmin is used from within a BundleActivator during deploy.

--
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