[jboss-jira] [JBoss JIRA] (WFLY-2605) TCCL leak in infinispan transaction reaper thread

[Paul Ferraro (JIRA)]

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

Paul Ferraro edited comment on WFLY-2605 at 12/8/13 12:08 PM:
--------------------------------------------------------------

[~brentdouglas] Please attach the hibernate configuration.  The cache manager in use should get destroyed on undeploy - and it looks like that isn't happening.  I need to know which region factory is being used.
                
      was (Author: pferraro):
    Please attach the hibernate configuration.  The cache manager in use should get destroyed on undeploy - and it looks like that isn't happening.  I need to know which region factory is being used.
                  
> TCCL leak in infinispan transaction reaper thread
> -------------------------------------------------
>
>                 Key: WFLY-2605
>                 URL: https://issues.jboss.org/browse/WFLY-2605
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, JPA / Hibernate
>    Affects Versions: 8.0.0.Beta1
>         Environment: Fedora 19, Oracle 7u45, Wildfly 7952aa65e67e1d
>            Reporter: Brent Douglas
>            Assignee: Paul Ferraro
>
> The reaper thread created in TransactionTable is leaking a deployment module classloader. I have observed by deploying and undeploying the same artifact a couple of times over that only the first deployment is held.
> Looking at where the thread is created in [TransactionTable|https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/transaction/TransactionTable.java?source=cc#L133] it looks to me like it will get the TCCL of the caller so either that should be changed in Infinispan or the caller TCCL should be set appropriately.
> !http://i.imgur.com/M37pHSe.png!

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