More than which distribution of RH, its kernel which matters. If you are using any 2.4.x kernel there seems some problem in native thread stack size. The ulimit setting will set it to required stack size limit. If you run long living thread and recursive fn, you can see the effect of these params. Your thread dies and you can browse a hell a lot of bugs in java site. Blackdown may be better but I havn't tried it. Moreover it Blackdown uses the same code of Hotspot then it may have the same problem.
The LD_ASSUME_KERNEL says the native thread library to use 2.2.5 thread library which is a pretty solid one. This is what I know and I would welcome If any linux/java GURUs can give more explanation about these params. ALSO IN FUTURE PLEASE DON"T JUST MENTION THE RH VERSION. IF YOU MENTION THE KERNEL VERSION, IT WOULD BETTER TO SHARE SOME THOUGHT ABOUT OUR PROBLEMS. Please do uname -a to get the version (for newbeeies) Reg Ved -----Original Message----- From: Man Chi Ly [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 15, 2001 1:44 PM To: [EMAIL PROTECTED] Subject: RE: java.lang.OutOfMemroyError On Thu, 15 Nov 2001, Veda Narayanan wrote: > Try these environment variable either in the script you start your app or in > java script > > ulimit -s 2048 > export LD_ASSUME_KERNEL=2.2.5 > export _JAVA_SR_SIGNUM=12 > > These are the thread parameters which will set your env for the latest > thread related kernel changes in linux kernel. These environment setting > will make your app stable even after you fix any memory leaks in your app. > >From what I've read, the first two tweaks don't apply to Red Hat Linux 6.2. The JDK INSTALLATION document on the JDK download page at java.sun.com is important to read if you [plan to] use the Sun JDK. To sourabh: Also, I haven't read any mention that the Blackdown JDK 1.3.1 requires similiar environment tweaks to function well (for most people). It's my preferred JVM for Linux, but I don't run any heavily-loaded servers (i.e. BEA certifies WebLogic on Sun JDK 1.3.1, so you'd have a trickier time getting them to support a Blackdown JDK configuration in production). :ml > Reg > Ved > > > -----Original Message----- > From: Alexander V. Konstantinou [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 15, 2001 7:50 AM > To: kulkarni sourabh > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: java.lang.OutOfMemroyError > > > Sounds like you have a memory leak in your program. Yes, it is possible > to have memory leaks even in Java programs. All you have to do is to > add objects to a collection type (map, set, list, etc) and then forget > to remove them, or null all references to the collection. > > There are several software tools available to assist in detecting such > leaks. I personally use OptimizeIt although I'm not sure if it is still > the best one out there. I think they have an evaluation version you can > download. Alternatively you can try to find the leak with a debugger > and/or print stataments. > > Alexander > > On Thu, Nov 15, 2001 at 03:32:33AM -0800, kulkarni sourabh wrote: > > Hi All, > > My application runs on celeron processor with 128MB > > RAM. OS- Redhat 6.2. I use Sun JDK1.3 currently. My > > application has around 5-6 threads running...but one > > of the thread stops after around 2-2.5 hrs of running. > > The message is > > java.lang.OutOfMemoryError: Unable to create new > > native thread > > java.lang.Thread.start(Native method) > > > > I searched through the net for 2 days but i haven't > > found the solution yet. I found that this is a listed > > bug at Sun and it's due to thread implementation on > > linux. > > > > I wanted to know whether using green threads can > > solve my problem? Also at Sun's bug parade, I found > > mention about Blackdown JDK being good implementation. > > With Sun jdk, I am using HotSpot Client VM .. and > > there is no help by setting Xms Xmx Xss or any of the > > parameters. The problem persists. > > Can using Blackdown JDK help me? > > Any help in very much appreciated, > > -sourabh > > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
