[jboss-jira] [JBoss JIRA] (WFLY-2856) Classloader leak caused by xnio-file-watcher

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFLY-2856:
-----------------------------------

    Fix Version/s: 8.0.0.Final
         Assignee: Stuart Douglas
      Component/s: Web (Undertow)


Stuart has a fix for this committed in undertow:

https://github.com/undertow-io/undertow/commit/e6fce8f29ab96a27bc9242d941c4f0729a8dcba5
                
> Classloader leak caused by xnio-file-watcher
> --------------------------------------------
>
>                 Key: WFLY-2856
>                 URL: https://issues.jboss.org/browse/WFLY-2856
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.CR1
>            Reporter: Harald Wellmann
>            Assignee: Stuart Douglas
>             Fix For: 8.0.0.Final
>
>
> After redeploying my application from Eclipe/JBoss Tools via "Full Publish" a couple of times in a row, I'm getting a PermGen OutOfMemoryError.
> In jvisualvm, I can see multiple threads named xnio-file-watcher, each having its context classloader set to the module classloader of my (undeployed) application. Probably the thread should be stopped (but isn't) when the application is undeployed.
> This leak only occurs with unzipped deployments.
> I also see these extra threads independent of Eclipse when copying an unzipped deployment to {{standalone/deployments}} and adding/removing the dodeploy/deployed marker files.

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