Are you using Oracle? We had the same problem. "OutOfMemoryError: unable to create new native thread" with no obvious explanation; we weren't anywhere near the OS thread limit or any other limit we could determine.
After a lot of experimentation, we finally traced the problem down to the Oracle OCI driver. Switching to the thin driver made the problem go away. It also cured a serious memory leak (about 1 GB every 36 hours) in the native code (Java heap was normal). We are using Oracle 9i RAC with the 9.2.0.1 jdbc driver for jdk 1.4. We didn't see the problem on Solaris - only Linux. We wanted to use the OCI driver to support Transparent Application Failover, but instead it seems to have provided only Chronic Application Failure :-( Jeff Schnitzer [EMAIL PROTECTED] The Sims Online > -----Original Message----- > From: Dennis Muhlestein [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 23, 2002 10:16 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] OutOfMemoryError: unable to create new native thread > > Hi All, > > We've launched! And we're using version 3.0.4 in Production. During > Development, we never had any problems, but now on the live servers, we > get the following exception. It's occurred 4 or 5 different times and > always has the same stack trace. There isn't any other output to help > figure out what's going on besides this though. > > > 2002-12-18 18:04:26,649 ERROR [STDERR] java.lang.OutOfMemoryError: > unable to create new native thread > 2002-12-18 18:04:26,649 ERROR [STDERR] at java.lang.Thread.start(Native > Method) > 2002-12-18 18:04:26,650 ERROR [STDERR] at > org.jnp.server.Main.listen(Main.java:311) > 2002-12-18 18:04:26,650 ERROR [STDERR] at > org.jnp.server.Main.run(Main.java:279) > 2002-12-18 18:04:26,650 ERROR [STDERR] at > java.lang.Thread.run(Thread.java:536) > > > We have to stop jboss and start it again when this happends. > > I'd like to find out more reliably how many threads are being used by > jboss. We don't have much load yet. "ps -u jboss | wc -l" is 52 right > now. It hasn't fluctuated much from that, but is that an accurate > number of threads being used? I saw some discussion on the development > list about number of threads being more than that but am not quite sure > the best way to tell. Any advise appreciated! > > Anyway, if anyone has experienced something similar and found a way > around it, I'd be very greatfull to hear. > > We're Using: > > sun-jdk 1.4.1.01 > gentoo linux > dual processor > 4 gigs memory > Here is the command line used when starting jboss: > > /opt/sun-jdk-1.4.1.01/bin/java-Xmx3072M-Dprogram.name=run.sh- > classpath/opt/jboss-3.0.4/bin/run.jar:/opt/sun-jdk- > 1.4.1.01/lib/tools.jarorg.jboss.Main > > > Thanks > Dennis > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
