[infinispan-issues] [JBoss JIRA] (ISPN-2962) Fix thread leaks in the core test suite

[Adrian Nistor (JIRA)]

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

Adrian Nistor updated ISPN-2962:
--------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1736

    
> Fix thread leaks in the core test suite
> ---------------------------------------
>
>                 Key: ISPN-2962
>                 URL: https://issues.jboss.org/browse/ISPN-2962
>             Project: Infinispan
>          Issue Type: Task
>          Components: Test Suite
>    Affects Versions: 5.2.5.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 5.3.0.Final
>
>
> The core test suite leaks several threads, which then keep their context classloaders alive and cause PermGen leaks.
> For example, I found these tests still alive at the end of a test run:
> {noformat}
> "Scheduled-eviction-thread-2486" daemon prio=10 tid=0x00007f2d6009e000 nid=0xecd waiting on condition [0x00007f2d48278000]
> "Scheduled-eviction-thread-2485" daemon prio=10 tid=0x00007f2d600b7800 nid=0xeb6 waiting on condition [0x00007f2d3f549000]
> "Scheduled-eviction-thread-2484" daemon prio=10 tid=0x00007f2d6005d000 nid=0xe9d waiting on condition [0x00007f2d22aca000]
> "AsyncStoreCoordinator-null" daemon prio=10 tid=0x0000000001cbf000 nid=0xb33 waiting on condition [0x00007f2d2b094000]
> "AsyncStoreCoordinator-null" daemon prio=10 tid=0x0000000001ca4000 nid=0xb1e waiting on condition [0x00007f2d3bbab000]
> "AsyncStoreCoordinator-null" daemon prio=10 tid=0x0000000001c9f000 nid=0xaee waiting on condition [0x00007f2db113b000]
> "AsyncStoreCoordinator-null" daemon prio=10 tid=0x0000000001cb7800 nid=0x8bf waiting on condition [0x00007f2d488d1000]
> "transport-thread-0,ReplSyncDistributedExecutorTest-NodeCD" daemon prio=10 tid=0x00007f2d64784000 nid=0x5308 waiting on condition [0x00007f2d7261d000]
> "transport-thread-0,DistributedExecutorWithCacheLoaderTest-NodeBN" daemon prio=10 tid=0x00007f2d64403800 nid=0x4b38 waiting on condition [0x00007f2d42a82000]
> "transport-thread-0,DistributedExecutorWithCacheLoaderTest-NodeBH" daemon prio=10 tid=0x00007f2d643f3800 nid=0x4840 waiting on condition [0x00007f2d35bf7000]
> "asyncTransportThread-0,ReplSyncDistributedExecutorWithTopologyAwareNodesTest-NodeAV" daemon prio=10 tid=0x00007f2d646a8800 nid=0x41ca waiting on condition [0x00007f2d3b552000]
> "transport-thread-0,DistributedExecutorWithCacheLoaderTest-NodeAP" daemon prio=10 tid=0x00007f2d644d6000 nid=0x3edc waiting on condition [0x00007f2d7290b000]
> "transport-thread-0,DistributedExecutorNonConcurrentTest-NodeAJ" daemon prio=10 tid=0x00007f2d645a0000 nid=0x3be6 waiting on condition [0x00007f2d39ce8000]
> "transport-thread-0,DistributedExecutorTest-NodeH" daemon prio=10 tid=0x00007f2d6406b000 nid=0x2af6 waiting on condition [0x00007f2d4261d000]
> "transport-thread-0,DistributedExecutorTest-NodeD" daemon prio=10 tid=0x00007f2d6410f000 nid=0x283f waiting on condition [0x00007f2d43e87000]
> "transport-thread-0,InDoubtXidReturnedOnceTest-NodeC" daemon prio=10 tid=0x00007f2d64621000 nid=0x188b waiting on condition [0x00007f2d4a988000]
> "Scheduled-eviction-thread-409" daemon prio=10 tid=0x00007f2d600b5000 nid=0x6ac3 waiting on condition [0x00007f2d2cbec000]
> "Scheduled-eviction-thread-403" daemon prio=10 tid=0x00007f2d600ad000 nid=0x6a35 waiting on condition [0x00007f2d2924e000]
> "Scheduled-eviction-thread-396" daemon prio=10 tid=0x00007f2d60089000 nid=0x698c waiting on condition [0x00007f2d30a6c000]
> "Scheduled-eviction-thread-390" daemon prio=10 tid=0x00007f2d60052000 nid=0x6903 waiting on condition [0x00007f2d3d703000]
> "pool-292-thread-2" prio=10 tid=0x00007f2d6c0bb000 nid=0x5cb3 waiting on condition [0x00007f2db0218000]
> "pool-292-thread-1" prio=10 tid=0x00007f2d6c073000 nid=0x5cb2 waiting on condition [0x00007f2d3aef9000]
> {noformat}

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