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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-1329:
-----------------------------------------------

Scott Mumford <smumford at redhat.com> made a comment on [bug 960497|https://bugzilla.redhat.com/show_bug.cgi?id=960497]

Emanue, can I ask you to provide some details for the 6.1.1 release notes? 

We need an outline of what was causing the problem to manifest, what change was implemented to fix it, and how the product behaves now to avoid the issue.

Thanks for any help you can offer.
                
> '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: Emanuel Muckenhuber
>             Fix For: 8.0.0.Alpha2
>
>         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