Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 11680 invoked from network); 13 Jun 2002 23:27:24 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Jun 2002 23:27:24 -0000 Received: (qmail 22455 invoked by uid 97); 13 Jun 2002 23:27:17 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 22440 invoked by uid 97); 13 Jun 2002 23:27:16 -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 22428 invoked by uid 98); 13 Jun 2002 23:27:16 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D092A50.4DF613C3@sun.com> Date: Thu, 13 Jun 2002 16:27:12 -0700 From: Eric Armstrong X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "tomcat-user@jakarta.apache.org" Subject: Tomcat 4.0 Manager Install -- Brittle?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've been using the ant install task to add a servlet to a Tomcat 4.0 container. Symptoms: 1) The install script hangs. 2) Tomcat crashes. 3) Catalina.out shows that the app threw an exception at startup. I understand having to fix my application, but its weird that I have to restart Tomcat after each failed attempt. Is that a known problem with the Manager? In 3.1, it was possible to update an app without having to restart Tomcat. Does that feature exist in 4.0? -- To unsubscribe, e-mail: For additional commands, e-mail: