Re: [infinispan-dev] Classloader leaks?
After looking into this some more...
TestNGTestListener does report 1262 leaked HotRodServerWorker and
MemcachedServer worker threads at the end of the compatibility-mode-it
test suite, so I'd say we probably do have a leak. The tests do seem
to shut down their servers at the end, maybe someone more familiar
with the server could look into why this happens? And maybe change the
thread naming scheme so that we can tell from the thread name which
test didn't shut down its servers properly?
But I'm pretty sure the leak isn't the problem here, compared to the
fact that we run 15 tests in parallel, AND each test starts 2
HotRod/Memcached/REST servers and 2 clients, AND they use the default
thread pool sizes instead of the 20x smaller thread pool sizes that we
use in the core suite.
Cheers
Dan
On Thu, Feb 23, 2017 at 9:56 AM, Vojtech Juranek <vjuranek(a)redhat.com> wrote:
On středa 22. února 2017 23:31:55 CET Sanne Grinovero wrote:
> Good point! You're right, I verified and all instances of e.g. the
> jgroups jar were using the same FD, just a different thread id.
yes, maybe there are some stale threads? Recently (well, actually it quite
some time and it's still on my TODO list to investigate it more:-) testsuite
started to fail with OOM issue "cannto create native thread" on some machines
(rarely on RHEL7, very often on RHEL6). I tried to increase limit on user
threads and end up with unlimited, so this sound like some leak to me as well.
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev