[jboss-jira] [JBoss JIRA] (WFLY-3280) Thread locking problem when app server is going to shutdown

[Ondřej Chaloupka (JIRA)]

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

Ondřej Chaloupka commented on WFLY-3280:
----------------------------------------

I moved the bug under wildfly as I found that it's more appropriate.
                
>  Thread locking problem when app server is going to shutdown
> ------------------------------------------------------------
>
>                 Key: WFLY-3280
>                 URL: https://issues.jboss.org/browse/WFLY-3280
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.1.0.CR1
>            Reporter: Ondřej Chaloupka
>            Assignee: David Lloyd
>         Attachments: server.dump, server.log
>
>
> I face problem that remoting thread and MSC service thread is deadlocked when server is going to shutdown.
> This happens in half of the cases when I run my integration arquillian tests again EAP 6.3.0 engineering releases.
> I deploy one testing application packaged as jar file and then jdbc driver is deployed by copying to deployments folder.
> I'm attaching server log file and thread dump at the time when threads are stuck.
> I was trying to find out where the lock occurs and from the stack trace it happens on two places. One is lock on remoting queue and other is lock on DeploymentRepository object.
> I did a quick fix which seems to work for me that I removed 'synchronized' keyword from the methods which remove listeners in DeploymentRepository.
> It means from:
> https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jboss/as/ejb3/deployment/DeploymentRepository.java#L103
> and
> https://github.com/jbossas/jboss-eap/blob/6.x/ejb3/src/main/java/org/jboss/as/ejb3/deployment/DeploymentRepository.java#L107
> I'm really not sure whether this is 'a correct' fix but I just put my observation here to have some starting point.
> This could not be trouble in remoting directly, maybe it's rather problem of MSC component. If so, please, change the jira type. Thank you.

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