[jboss-jira] [JBoss JIRA] Updated: (JBAS-6815) org.jboss.test.jca.test.TxConnectionManagerStressTestCase creates too many threads

[David Lloyd (JIRA)]

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

David Lloyd updated JBAS-6815:
------------------------------

    Environment: 
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)

and also

java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)


Linux 2.6.27.12-78.2.8.fc9.x86_64 #1 SMP Mon Jan 19 19:25:03 EST 2009 x86_64 x86_64 x86_64 GNU/Linux



> org.jboss.test.jca.test.TxConnectionManagerStressTestCase creates too many threads
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-6815
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6815
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>         Environment: java version "1.6.0_12"
> Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
> Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)
> and also
> java version "1.6.0_12"
> Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
> Linux 2.6.27.12-78.2.8.fc9.x86_64 #1 SMP Mon Jan 19 19:25:03 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: David Lloyd
>            Assignee: David Lloyd
>
> The exception is:
> 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.jboss.test.jca.test.TxConnectionManagerStressTestCase.doBlocking(TxConnectionManagerStressTestCase.java:398)
>         at org.jboss.test.jca.test.TxConnectionManagerStressTestCase.testBlockingAggressiveRemovalAndFillTrackByTx(TxConnectionManagerStressTestCase.java:212)
>         at org.jboss.test.util.ejb.EJBTestCase.runBare(EJBTestCase.java:214)
>         at org.jboss.test.util.ejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:202)
>         at org.jboss.test.util.ejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:107)
>         at org.jboss.test.util.ejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:85)
>         at org.jboss.invocation.Invocation.performCall(Invocation.java:386)
>         at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:228)
>         at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:156)
>         at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
>         at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
>         at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173)
>         at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
>         at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:173)
>         at org.jboss.ejb.plugins.SecurityInterceptor.process(SecurityInterceptor.java:228)
>         at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:211)
>         at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:97)
>         at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invoke(PreSecurityInterceptor.java:81)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:650)
>         at org.jboss.ejb.Container.invoke(Container.java:1029)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:232)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
>         at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:551)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
> It comes from the point where the doBlocking() method creates client threads for its tests... so perhaps it's just creating too many?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira