[jboss-jira] [JBoss JIRA] (WFLY-1329) 'whoami' operation unexpectedly requires the domain wide configuration lock

Thu May 9 23:24:54 EDT 2013

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

Osamu Nagano edited comment on WFLY-1329 at 5/9/13 11:22 PM:
-------------------------------------------------------------

Attached 'slowdeployweb.war' just sleeps for 1 hour in javax.servlet.ServletContextListener#contextDestroyed() to emulate a long undeployment.

      was (Author: osamu.nagano):
    It sleeps for 1 hour at javax.servlet.ServletContextListener#contextDestroyed().

> 'whoami' operation unexpectedly requires the domain wide configuration lock
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-1329
>                 URL: https://issues.jboss.org/browse/WFLY-1329
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>         Environment: 7.2.0.Final (EAP 6.1.0.Beta1)
>            Reporter: Osamu Nagano
>            Assignee: Brian Stansberry
>         Attachments: slowdeployweb.war
>
>
> 'whoami' operation in domain mode seems to require the domain wide configuration lock.  This is problematic when there is an editing operation of domain.xml like a long running undeployment because all 'whoami' requests are blocked by the existing task.  The number of blocked thread increases indefinitely and it will cause an OutOfMemoryError.
> It doesn't happen in standalone mode.

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