Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 74983 invoked by uid 500); 29 May 2001 20:15:57 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 74936 invoked from network); 29 May 2001 20:15:55 -0000 Received: from unknown (HELO server01.hh.uptime-isc.de) (217.6.61.26) by h31.sny.collab.net with SMTP; 29 May 2001 20:15:55 -0000 Received: by server01.hh.uptime-isc.de with Internet Mail Service (5.5.2650.21) id ; Tue, 29 May 2001 14:35:29 +0200 Message-ID: From: Ralph Einfeldt To: "'tomcat-user@jakarta.apache.org'" Subject: AW: Tomcat Web Server 3.1 bug Date: Tue, 29 May 2001 14:35:24 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Change catch( Exception e ) to catch( Throwable e ) to see which kind of error you get. There are Throwables that are not Exceptions=20 (java.lang.Error and all of it's subclasses) If your problem lies in a tomcat 3.1 bug, you won't=20 have much fun. You just can try to avoid the=20 offending code. (Or convince your provider to upgrade. As tomcat 3.1 is known as quite buggy, I think this is recommended anyway) By the way, I think it's not a good idea to define a=20 variable with the name 'session'. With that you hide=20 the implicit session object of jsp. -----Urspr=FCngliche Nachricht----- Von: Vishal Batra [mailto:vishalbatra_@rediffmail.com] Gesendet: Dienstag, 29. Mai 2001 14:00 An: tomcat-user@jakarta.apache.org Betreff: Tomcat Web Server 3.1 bug