You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2010/11/30 21:20:11 UTC

[jira] Resolved: (OPENJPA-1898) TestQueryMultiThreaded fails with OOME "unable to create new native thread"

     [ https://issues.apache.org/jira/browse/OPENJPA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick resolved OPENJPA-1898.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0
                   2.1.0
         Assignee: Michael Dick

Thanks for the patch Mark, I've committed it to trunk and 2.1.x. 


> TestQueryMultiThreaded fails with OOME "unable to create new native thread"
> ---------------------------------------------------------------------------
>
>                 Key: OPENJPA-1898
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1898
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>            Reporter: Mark Struberg
>            Assignee: Michael Dick
>             Fix For: 2.1.0, 2.2.0
>
>         Attachments: OPENJPA-1898.patch
>
>
> here comes the stacktrace:
> <error message="unable to create new native thread" type="java.lang.OutOfMemoryError">java.lang.OutOfMemoryError: unable to create new native thread
>         at java.lang.Thread.start0(Native Method)
>         at java.lang.Thread.start(Thread.java:597)
>         at org.apache.openjpa.slice.TestQueryMultiThreaded.testHeavyLoad(TestQueryMultiThreaded.java:236)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at junit.framework.TestCase.runTest(TestCase.java:154)
> reducing the thread count to 800 should help to prevent this problem. This might be caused to the 1024 processes ulimit on most linux installations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.