Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 51093 invoked from network); 1 Nov 2001 17:26:40 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 1 Nov 2001 17:26:40 -0000 Received: (qmail 22144 invoked from network); 1 Nov 2001 17:28:56 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 1 Nov 2001 17:28:56 -0000 Received: (qmail 22924 invoked by uid 97); 1 Nov 2001 17:25:46 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 22908 invoked by uid 97); 1 Nov 2001 17:25:45 -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 22891 invoked from network); 1 Nov 2001 17:25:45 -0000 Message-ID: <4135D07B3996D1118F3100805F8B0B0E02BC8732@apollo.tecnomen.ie> From: Donie Kelly To: 'Tomcat Users List' Subject: RE: Filters in Tomcat 4.0 Date: Thu, 1 Nov 2001 17:17:42 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sorry Craig but I would have include more information if I had it... Basically, no exceptions are thrown. It just acts as if the filter is not there. Subsequent requests work fine. What more can I say? Donie -----Original Message----- From: Craig R. McClanahan [mailto:craigmcc@apache.org] Sent: 01 November 2001 16:48 To: Tomcat Users List Subject: Re: Filters in Tomcat 4.0 On -1 xxx -1, Donie Kelly wrote: > From: Donie Kelly > Reply-To: Tomcat Users List > To: tomcat-user@jakarta.apache.org > Subject: Filters in Tomcat 4.0 > > We have a filter attached to a servlet. Works fine except that on > initial startup of Tomcat the filter fails to run the first time. It > works on subsequent requests without problems though. > What does "fails to run" mean? Does it throw an exception? It's difficult to respond to a question like this without a lot more details. > Any idea my the first request is a problem? > Regards > Donie > Craig -- To unsubscribe: For additional commands: Troubles with the list: -- To unsubscribe: For additional commands: Troubles with the list: