tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Smith <>
Subject Re: startup and core dump
Date Mon, 21 Jan 2002 18:40:26 GMT
JDK 1.4?  I haven't worked with that yet since last I checked it was still a 
beta release.   As far as the ulimit... line goes, I was being literal 
(except for the quote marks :-).  At least that's the command for the bash 
shell to limit stack space for executed commands.  It may be different 
depending on the shell you use and I thought the seg fault problem was fixed 
in 1.4.  Maybe not??  Hopefully someone more familiar with the Bug Parade on 
JDK 1.4 can offer some insight.

Anyway, if you use it, just make sure it's before the java.... command that 
actually starts Tomcat itself.  I put it in the script before the 
call to since that's how I start Tomcat on the dev machine.  It's 
in the script for starting tomcat from /etc/init.d as well on my production 
server (Mandrake 8).


On Monday 21 January 2002 12:40 pm, you wrote:
> At 10:27 AM 1/21/02 -0500, you wrote:
> >I believe this one is well documented, but there is an issue with JDK
> > 1.3.x and Linux where a stack set to unlimited will cause a seg fault. 
> > To fix, use 'ulimit -s 2048' in either or
> >
> >If this doesn't fix it, please post more info (OS dist, JDK version, exact
> >error text, etc...)
> >
> >--David
> I am using JDK1.4.  Would you expand on what "use 'unlimit -s 2048' in
> either or" means in practice?  Where do I put that
> in, if you are being literal?  Or, if you are not being literal,
> do I just put it in the command line?
> Should I go back to JDK1.3.1?  I really like the new stuff in JDK1.4 and
> would like to use that if there is a possibility.
> Thanks for your help.
> - Micael
> --
> To unsubscribe:   <>
> For additional commands: <>
> Troubles with the list: <>

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message