This is something I banged my head on for days. I did a good amount of strace and stuff to figure it out. Of course, none of the stuff I did helped the problem. Have you read the release notes for Tomcat? Evidentally there is an issue with Linux that can be corrected by running the following command. ulimit -s 2048 It sets the stack site of your session (is what I gather from the man on it)... Can't promise this will fix your problem, but I had 4 different linux boxes (3 different people) who had the same issue, and this fixed it! Good luck! Joseph Hobbs hobbsj@somecrazyfool.com -----Original Message----- From: James Bliss [mailto:bliss@attbi.com] Sent: Sunday, December 23, 2001 5:46 PM To: suse-linux-e@suse.com Subject: [SLE] Tomcat 4.0 Has anyone had any luck installing Tomcat 4.0 on their SuSE box? This is a little more complicated than just the installation. I am also talking about integrating tomcat with Apache and using the _webapp_ module for a seamless integration (no need for the 8080 port when going through apache). I tried this about a month ago. I have not tried since the glibc update from SuSE and do not know if that will help. I followed all of the tomcat documentation and I could never get it to work. I have been able to get tomcat 3.3 running with mod_jk, but not 4.0 with _webapp_. Thanks, Jim -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com