Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 72128 invoked from network); 16 Jul 2003 10:49:06 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 16 Jul 2003 10:49:06 -0000 Received: (qmail 3939 invoked by uid 97); 16 Jul 2003 10:51:33 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 3932 invoked from network); 16 Jul 2003 10:51:33 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 16 Jul 2003 10:51:33 -0000 Received: (qmail 70652 invoked by uid 500); 16 Jul 2003 10:48:48 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 70639 invoked from network); 16 Jul 2003 10:48:48 -0000 Received: from sid.armstrong.com (204.74.20.252) by daedalus.apache.org with SMTP; 16 Jul 2003 10:48:48 -0000 Received: from joedog.org (fnord.armstrong.com [204.74.20.11]) by sid.armstrong.com (8.12.8p1/8.12.8) with ESMTP id h6GAgLM0023862 for ; Wed, 16 Jul 2003 05:42:21 -0500 Message-ID: <3F152D88.8070701@joedog.org> Date: Wed, 16 Jul 2003 06:48:40 -0400 From: Tim Funk Organization: Human being User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en, es-mx, de, sv MIME-Version: 1.0 To: Tomcat Users List Subject: Re: AW: Tomcat 4.1.24 + Security Manager + weird Exceptions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N How do you mean survive? The JVM core dumps (which then is a JVM vendor issue) or the JVM stays up buit sits there uselessly? -Tim Haug Thomas wrote: > Hi Tim, > > thanks for the advise. > The interesting part is that tomcat (process) doesn't seem to survive the > re-initialization of the ServerSocket. It this a known bug? > > Regards, > Thomas > >>-----Urspr�ngliche Nachricht----- >>Von: Tim Funk [mailto:funkman@joedog.org] >>Gesendet am: Dienstag, 15. Juli 2003 13:02 >>An: Tomcat Users List >>Betreff: Re: Tomcat 4.1.24 + Security Manager + weird Exceptions >> >>- man ulimit >>- Google (java "Too many open files" solaris) >> >>-Tim >> --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org