You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Benjamin Cox <be...@bjtechnics.com> on 2003/05/21 23:46:14 UTC

Tomcat 4, Apache, "manager" webapp

  Has anyone gotten the tomcat "manager" webapp to work with Apache?  
  I've searched around a fair bit, but haven't found a conclusive 
answer.  Perhaps there isn't one :-)  If there's a more appropriate list 
to ask this, please steer me that way and accept my apologies.
  I'm using RedHat 7.2, Apache 1.3.20, Tomcat 4.1.24, mod_webapp (from 
cvs 5/19/03).  So far, I've only been able to make it work on Tomcat 
standalone, and any activities I do through that interface do not seem 
to affect my webapp's context running on Apache at port 80 at all. When 
I restart or redeploy an application's context, Apache doesn't notice, 
and continues to serve the old version of the application.
  Seems to me, therefore, that Apache (via mod_webapp) is serving its 
own instances of any contexts configured in Apache's httpd.conf file. 
 So, I added a directive:

    WebAppDeploy manager warpConnection /manager

  to the appropriate Virtual Host in my httpd.conf, and attempted to go 
to http://servername/manager/html, but I got the error:

java.lang.SecurityException: Servlet of class org.apache.catalina.servlets.HTMLManagerServlet is privileged and cannot be loaded by this web application

  I interpret this to mean that the JVM isn't getting any authentication 
data with my request, which it would normally be getting through Tomcat 
standalone.  It seems that Tomcat somehow knows to initiate basic 
authentication whenever I request a /manager url, but Apache doesn't. 
 Is there any way that I can tell Apache to authenticate people who are 
trying to connect to the /manager web application?  If I do, will it 
know how to pass that authentication information to Tomcat via 
mod_webapp?  Will this create the proper credentials in the JVM to allow 
me to load this code?  Or, am I on the wrong track altogether?
  By the way, our real goal is to be able to 
start/stop/reload/deploy/undeploy from within our ant build file.
  Thanks for any assistance, and for an excellent app server,

    Ben


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


RE: Tomcat 4, Apache, "manager" webapp

Posted by Bill Castle <bi...@logcastle.com>.
Ben,

I saw your IM about the twp symbolic link. I've got no problems with
changing it.

-bill

-----Original Message-----
From: Benjamin Cox [mailto:ben@bjtechnics.com]
Sent: Wednesday, May 21, 2003 2:46 PM
To: tomcat-user@jakarta.apache.org
Subject: Tomcat 4, Apache, "manager" webapp


  Has anyone gotten the tomcat "manager" webapp to work with Apache?
  I've searched around a fair bit, but haven't found a conclusive
answer.  Perhaps there isn't one :-)  If there's a more appropriate list
to ask this, please steer me that way and accept my apologies.
  I'm using RedHat 7.2, Apache 1.3.20, Tomcat 4.1.24, mod_webapp (from
cvs 5/19/03).  So far, I've only been able to make it work on Tomcat
standalone, and any activities I do through that interface do not seem
to affect my webapp's context running on Apache at port 80 at all. When
I restart or redeploy an application's context, Apache doesn't notice,
and continues to serve the old version of the application.
  Seems to me, therefore, that Apache (via mod_webapp) is serving its
own instances of any contexts configured in Apache's httpd.conf file.
 So, I added a directive:

    WebAppDeploy manager warpConnection /manager

  to the appropriate Virtual Host in my httpd.conf, and attempted to go
to http://servername/manager/html, but I got the error:

java.lang.SecurityException: Servlet of class
org.apache.catalina.servlets.HTMLManagerServlet is privileged and cannot be
loaded by this web application

  I interpret this to mean that the JVM isn't getting any authentication
data with my request, which it would normally be getting through Tomcat
standalone.  It seems that Tomcat somehow knows to initiate basic
authentication whenever I request a /manager url, but Apache doesn't.
 Is there any way that I can tell Apache to authenticate people who are
trying to connect to the /manager web application?  If I do, will it
know how to pass that authentication information to Tomcat via
mod_webapp?  Will this create the proper credentials in the JVM to allow
me to load this code?  Or, am I on the wrong track altogether?
  By the way, our real goal is to be able to
start/stop/reload/deploy/undeploy from within our ant build file.
  Thanks for any assistance, and for an excellent app server,

    Ben


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org