]
Scott Marlow commented on ISPN-1890:
------------------------------------
Does anyone have a workaround? This happens everytime that I try to build on Linux with
Oracle jdk 1.6.0_26 or 1.6.0_31. Also tried "MAVEN_OPTS=-Xmx1024m -Xms512m
-XX:MaxPermSize=128m"
It sounds like a leak to me but I'm not sure why I'm the only one hitting this
(Galder only experienced this once and it went away).
Unable to create new native thread when running core/ testsuite
---------------------------------------------------------------
Key: ISPN-1890
URL:
https://issues.jboss.org/browse/ISPN-1890
Project: Infinispan
Issue Type: Bug
Components: Test Suite
Reporter: Galder ZamarreƱo
Assignee: Mircea Markus
Fix For: 5.2.0.FINAL
Attachments: output.log
Suddenly, running core/ testsuite only with -Xmx768m -XX:MaxPermSize=256M, I'm
seeing:
{code}Test suite progress: tests succeeded: 1695, failed: 4, skipped: 0.
Exception in thread "ConnectionMap.Acceptor,null,null"
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:658)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568)
at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354)
at
org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259)
at java.lang.Thread.run(Thread.java:680)
Exception in thread "ConnectionMap.Acceptor,null,null"
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:658)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568)
at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354)
at
org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259)
at java.lang.Thread.run(Thread.java:680)
Exception in thread "ConnectionMap.Acceptor,null,null"
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:658)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568)
at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411)
at
org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354)
at
org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259)
at java.lang.Thread.run(Thread.java:680)
[testng-TopologyAwareDistAsyncFuncTest] Test
testPutIfAbsentFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest)
succeeded.
Test suite progress: tests succeeded: 1696, failed: 4, skipped: 0.
[testng-TopologyAwareDistAsyncFuncTest] Test
testRemoveFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest)
succeeded.
Test suite progress: tests succeeded: 1697, failed: 4, skipped: 0.
[testng-TopologyAwareDistAsyncFuncTest] Test
testReplaceFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest)
succeeded.
Test suite progress: tests succeeded: 1698, failed: 4, skipped: 0.
Exception in thread
"CacheViewTrigger,TopologyAwareDistAsyncFuncTest-NodeA-38647"
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:658)
at
java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(ThreadPoolExecutor.java:727)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:657)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92)
at
org.infinispan.cacheviews.CacheViewsManagerImpl$ViewTriggerThread.run(CacheViewsManagerImpl.java:848){code}
See attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: