Return-Path: 
 <tomcat-user-return-4010-qmlist-jakarta-archive-tomcat-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 69543 invoked from network); 5 Dec 2001 19:57:23 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 5 Dec 2001 19:57:23 -0000
Received: (qmail 1993 invoked by uid 97); 5 Dec 2001 19:48:08 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org
Received: (qmail 1967 invoked by uid 97); 5 Dec 2001 19:48:07 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 15637 invoked from network); 5 Dec 2001 19:37:00 -0000
Message-ID: <ABC3DD304107D511B4D40002B32C1CF50AD532@brkmail01.adirtech.com>
From: Mark Saltzman <msaltzman@adirtech.com>
To: "'tomcat-user@jakarta.apache.org'" <tomcat-user@jakarta.apache.org>
Subject: RE: Exception using Tomcat4.0 Manager
Date: Wed, 5 Dec 2001 14:26:31 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17DC2.BE336050"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C17DC2.BE336050
Content-Type: text/plain;
	charset="iso-8859-1"



	Just this morning I figured what the problem was. I had my own
server.xml file   that did not have the manager context defined. The line I
put in was (from tomcat4.0.1 final release):

<Context path="/manager" docBase="manager" debug="0" privileged="true"/>
	The privileged=true is the attribute that made it all work.

I did receive 2 responses that referred to other possible solutions.
1) Someone said they saw this problem if servlet.jar was in
$JAVA_HOME/jre/lib/ext
2) The manager context must be defined in each Virtual host for it to apply
to all the contexts in that host and only that host.

good luck,

mss

-----Original Message-----
From: Jeff Macomber [mailto:JMacomber@NetByTel.com]
Sent: Wednesday, December 05, 2001 11:46 AM
To: 'msaltzman@adirtech.com'
Subject: Exception using Tomcat4.0 Manager


Mark,

I saw your posting on the tomcat4 mailing list concerning the internal
server error on manager servlet.  I am experiencing the same problem.  I was
hoping you had found a solution to this problem since I didn't see any
replies posted to your message.  If you did find a solution could you send
me a reply with the steps to correct the problem.  Below is the specific
error:

javax.servlet.ServletException: Error allocating a servlet instance 
Root Cause:
java.lang.SecurityException: Servlet of class
org.apache.catalina.servlets.ManagerServlet is privileged and cannot be
loaded by this web application 

Thanks,

Jeff Macomber
NetByTel, Inc.
Boca Raton, FL

------_=_NextPart_001_01C17DC2.BE336050--