I received this error when I didn't have the manager context defined in the virtual host that I was trying to use to connect to it. I did have it defined for another virtual host, but it needed to be defined for each vh where I was using it.
One thing that I have noticed that is not in the documentation is that manager commands apply to the current virtual host, not to all instances of the 'path'. So in cases where you share the same context for different virtual hosts with the same path, each needs to be reloaded(start/stop/etc) from its own virtual host. I think this is important and should be clarified in the documentation as it just appeared to me that the manager was not working(context was not reloading) when actually I was using manager from one virtual host(what I consider my primary vh) and trying to load a page from the other. After playing around with it, I finally figured out what was going on. yes, I realize now that the manager/list does say 'listed app for virtual host xxx',but to me at first glance I just thought it was listing the contexts for any virtual host as I hadn't at that time turned off the auto-loading of contexts in my webapps directory. And it does make sense once you think about it...but I guess for some reason I think of 'manager' as a tomcat-level admin tool, not a virtual host-level context providing admin features. Charlie > -----Original Message----- > From: Mark Saltzman [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 03, 2001 10:01 AM > To: 'Craig R. McClanahan '; 'Tomcat Users List ' > Subject: RE: Exception using Tomcat4.0 Manager > > > Craig, > Thanks for the reply. The servlet.jar file was in the jre/lib/ext > directory! I took it out and restarted tomcat, but came up > with the same > problem. I also did a find on servlet.jar in TOMCAT_HOME and > found only the > one instance in common/lib. I reset my CLASSPATH (which > should not make a > difference, but I did it anyway) and restarted tomcat - same message. > > Any other suggestions would be appreciated. > > mss > > -----Original Message----- > From: Craig R. McClanahan > To: Tomcat Users List > Sent: 12/2/01 7:55 PM > Subject: Re: Exception using Tomcat4.0 Manager > > 99% of the cases of this exception that I have seen are > caused by having > a > copy of servlet.jar in the Java system extensions directory > ($JAVA_HOME/jre/lib/ext). You should not have it there. > > Craig > > > On Fri, 30 Nov 2001, Mark Saltzman wrote: > > > Date: Fri, 30 Nov 2001 15:21:42 -0500 > > From: Mark Saltzman <[EMAIL PROTECTED]> > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> > > Subject: Exception using Tomcat4.0 Manager > > > > I am using Tomcat4.0 on solaris and want to stop and start my > > application via the manager application. I put a new manager role > entry in > > my tomcat-users.xml file and went to the following url to test the > basic > > list command: > > > > http://zebra2:8081/manager/list > > > > I get back an Internal Server 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 > > ======================== > > > > What do I need to do to get this working? > > > > Mark Saltzman > > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
