OutOfMemoryError: unable to create new native thread
gquintana Feb 21, 2006 10:19 AMHello,
I get an exception java.lang.OutOfMemoryError: unable
to create new native thread under heavy conditions. I tried to increase Java memory size with -Xmx1024M option but it didn't help.
Here is the stack trace:
2006-02-21 10:22:34,272 INFO [STDOUT] java.lang.OutOfMemoryError: unable to create new native thread 2006-02-21 10:22:34,273 INFO [STDOUT] at java.lang.Thread.start(Native Method) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.transport.tcp.TCPChannel.free(TCPChannel.java:322) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.server.UnicastRef.free(UnicastRef.java:402) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.server.UnicastRef.done(UnicastRef.java:419) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.transport.DGCImpl_Stub.dirty(Unknown Source) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.transport.DGCClient$EndpointEntry.makeDirtyCall(DGCClient.java:328) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.transport.DGCClient$EndpointEntry.access$1600(DGCClient.java:144) 2006-02-21 10:22:34,273 INFO [STDOUT] at sun.rmi.transport.DGCClient$EndpointEntry$RenewCleanThread.run(DGCClient.java:539) 2006-02-21 10:22:34,273 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534) 2006-02-21 10:22:37,097 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected Error in method: public abstract void fr.gtietransport.myrabel.serveur.gestionUtilisateurs.bean.UtilisateursFacade.signalerPresence(fr.gtietransport.myrabel.serveur.gestionUtilisateurs.bo.UtilisateurBo) throws fr.gtietransport.lugdunum.serveur.biz.BusinessException,java.rmi.RemoteException java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start(Native Method) at java.util.Timer.<init>(Timer.java:95) at org.jboss.ejb.txtimer.TimerImpl.startInTx(TimerImpl.java:328) at org.jboss.ejb.txtimer.TimerImpl.startTimer(TimerImpl.java:108) at org.jboss.ejb.txtimer.TimerServiceImpl.createTimer(TimerServiceImpl.java:207) at org.jboss.ejb.txtimer.TimerServiceImpl.createTimer(TimerServiceImpl.java:121) at org.jboss.ejb.StatelessSessionEnterpriseContext$TimerServiceWrapper.createTimer(StatelessSessionEnterpriseContext.java:255) at fr.gtietransport.myrabel.serveur.gestionUtilisateurs.bean.UtilisateursFacadeBean.signalerPresence(UtilisateursFacadeBean.java:168) at sun.reflect.GeneratedMethodAccessor464.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:214)
I am using:
- JBoss 4.0.1SP1
- Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
- Red Hat Enterprise Linux 3 (Kernel 2.4.21-32.ELsmp)
Is it the bug JBAS-1369 described in Jira (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=65857)?
I didn't do the LD_ASSUME_KERNEL thing described in http://wiki.jboss.org/wiki/Wiki.jsp?page=LinuxThreadingModel, can it be related to my problem?
Thanks for your help,
Cheers,
Gérald