DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31439>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31439

Manager webapp cannot undeploy/redeploy webapps webapp

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |
            Summary|Manager webapp cannot       |Manager webapp cannot
                   |undeploy defunct webapp     |undeploy/redeploy webapps
                   |                            |webapp



------- Additional Comments From [EMAIL PROTECTED]  2004-10-11 17:18 -------
I marked this bug INVALID because I thought my original description was
misleading to say the least.

However, others seem to have similar problems, so I am reopening it, and will
try to provide a better description.

First of all, it has nothing to do with the webapp not working. Tomcat 5.5
simply will not delete/overwrite expanded webapplications.

On http://jakarta.apache.org/tomcat/tomcat-5.5-doc/deployer-howto.html

It is stated:
---------
Redeployment of a web application which has been deployed from a WAR when the
WAR is updated: the expanded web application is removed, and the WAR is expanded
again. This will not happen if the host is configured so that WARs are not
expanded, in which case the webapp will be simply redeployed.
---------

The part about removing the expanded webapp never happens.

As a workaround, I've configured Tomcat to not expand wabapps, so now (after
deleting the expanded webapp manually) undeployment and redeployment works.

First I tried to change this using the Admin webapp. That change was lost when
the server was restarted. Now I've added this line in "Tomcat 5.5/conf/server.xml":
  <Host appBase="webapps" name="localhost" unpackWARs="false" /> 
That solves the problem - if you can live with the webapps not being expanded.

The complete server.xml now looks loke this:
<Server>
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /> 
  <Listener
     className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> 
  <GlobalNamingResources>
    <Environment name="simpleValue" type="java.lang.Integer" value="30" /> 
    <Resource auth="Container"
              description="User database that can be updated and saved"
              name="UserDatabase" type="org.apache.catalina.UserDatabase"
              pathname="conf/tomcat-users.xml"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory" /> 
  </GlobalNamingResources>
  <Service name="Catalina">
    <Connector port="8080" redirectPort="8443"
               maxSpareThreads="75" maxThreads="150" minSpareThreads="25" /> 
    <Connector port="8009" protocol="AJP/1.3"
               protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"
               redirectPort="8443" /> 
    <Engine defaultHost="localhost" name="Catalina">
      <Host appBase="webapps" name="localhost" unpackWARs="false" /> 
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm" /> 
    </Engine>
  </Service>
</Server>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to