RE: Manager app in 4.1.27 behaves differently to 4.1.18
Thanks for confirming that. I just tried setting the unpackWARs to false and now 4.1.27 behaves just like 4.1.18. I did think i was going mad though.. -Original Message- From: Larry Isaacs [mailto:[EMAIL PROTECTED] Sent: 25 November 2003 17:59 To: Tomcat Users List Subject: RE: Manager app in 4.1.27 behaves differently to 4.1.18 I believe the point that Yoav was going to make was that Tomcat 4.1.18 doesn't honor the unpackWARs Host setting when using the Manager's deploy function. Thus it always serves such a webapp from the WAR, for which the Manager undeploy works. Tomcat 4.1.27 does honor the unpackWARs setting, so the same deploy command results in an auto-expanded webapp, if unpackWARs=true. I believe the Manager undeploy command in both 4.1.18 and 4.1.27 has trouble removing an auto-expanded WAR. If you set unpackWARs=false in 4.1.27, you would get the same behavior with respect to deploying and undeploying that you saw in Tomcat 4.1.18. Cheers, Larry -Original Message- From: Tom Lyle [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 10:18 AM To: Tomcat Users List Subject: RE: Manager app in 4.1.27 behaves differently to 4.1.18 Hi, I've reduced my server.xml down to the bare minumum of ROOT, manager admin contexts I use a copy of the same server.xml in an instance of Tomcat 4.1.27 Tomcat 4.1.18 and use the org.apache.catalina.ant.DeployTask to deploy my war file. In 4.1.18 it unpacks it into \work\localhost\myapp in 4.1.27 it unpacks it into \webapps\myapp (it also creates an empty myapp dir in \work\localhost ) in 4.1.27 the UndeployTask will not work because it can't remove the myapp dir in the webapp directory. The server.xml i used in both cases is attached bellow I'm totally at a loss as to whats going on Tom ?xml version='1.0' encoding='utf-8'? Server className=org.apache.catalina.core.StandardServer debug=0 port=8005 shutdown=SHUTDOWN Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycle Listener debug=0/ GlobalNamingResources Environment name=simpleValue override=true type=java.lang.Integer value=30/ Resource auth=Container description=User database that can be updated and saved name=UserDatabase scope=Shareable type=org.apache.catalina.UserDatabase/ ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources Service className=org.apache.catalina.core.StandardService debug=0 name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=100 bufferSize=2048 connectionTimeout=2 debug=9 disableUploadTimeout=true enableLookups=true maxProcessors=75 minProcessors=5 port=8080 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=10 bufferSize=2048 connectionTimeout=2 debug=0 disableUploadTimeout=false enableLookups=true maxProcessors=75 minProcessors=5 port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone Host className=org.apache.catalina.core.StandardHost appBase=webapps autoDeploy=true configClass=org.apache.catalina.startup.ContextConfig contextClass=org.apache.catalina.core.StandardContext debug=0 deployXML=true errorReportValveClass=org.apache.catalina.valves.ErrorReportValve liveDeploy=true mapperClass=org.apache.catalina.core.StandardHostMapper name=localhost unpackWARs=true Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=0 displayName=Tomcat Administration Application docBase=../server/webapps/admin mapperClass=org.apache.catalina.core.StandardContextMapper path=/admin privileged=true reloadable=false swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper Logger className
RE: Manager app in 4.1.27 behaves differently to 4.1.18
Howdy,
Is unpackWARs set to true for your Host?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Tom Lyle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 7:54 AM
To: Tomcat Users List
Subject: Manager app in 4.1.27 behaves differently to 4.1.18
Hi there,
I'm having a slightly annoying problem using the Tomcat Manager
application.
I have a webservices web application that i deploy using an Ant script
and
the org.apache.catalina.ant.DeployTask UndeployTask. On Tomcat 4.1.18
this
works fine, I package the application up as a war file and can deploy,
undeploy and redeploy with no problems - the war file gets unpacked
into
{CATALINA-HOME}\work\Standalone\localhost\myapp
However, i've upgraded to Tomcat 4.1.27 and now the ant script no
longer
works. When I deploy the war file using the manager it unpacks it into
{CATALINA-HOME}\webapps\myapp folder instead. This is irritating
because
when I try and redeploy the war file (i.e call undeploy then deploy
in
the
ant script) i get the message Cannot remove document base for path
/myapp
Why does 4.1.27 unpack its war files into the web app folder unlike
4.1.18?
I've tried replacing the server.xml file with the one from 4.1.18 but
it
still does the same thing. Is there a setting that I need to make
4.1.27
behave in the same way as 4.1.18?
Thanks
Tom
Limehouse Court, 3-11 Dod Street
London E14 7EQ Tel: 020 7537 8515
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Manager app in 4.1.27 behaves differently to 4.1.18
=.txt timestamp=true
verbosity=1/
Realm className=org.apache.catalina.realm.UserDatabaseRealm
debug=0 resourceName=UserDatabase validate=true/
/Engine
/Service
/Server
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 25 November 2003 14:04
To: Tomcat Users List
Subject: RE: Manager app in 4.1.27 behaves differently to 4.1.18
Howdy,
Is unpackWARs set to true for your Host?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Tom Lyle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 7:54 AM
To: Tomcat Users List
Subject: Manager app in 4.1.27 behaves differently to 4.1.18
Hi there,
I'm having a slightly annoying problem using the Tomcat Manager
application.
I have a webservices web application that i deploy using an Ant script
and
the org.apache.catalina.ant.DeployTask UndeployTask. On Tomcat 4.1.18
this
works fine, I package the application up as a war file and can deploy,
undeploy and redeploy with no problems - the war file gets unpacked
into
{CATALINA-HOME}\work\Standalone\localhost\myapp
However, i've upgraded to Tomcat 4.1.27 and now the ant script no
longer
works. When I deploy the war file using the manager it unpacks it into
{CATALINA-HOME}\webapps\myapp folder instead. This is irritating
because
when I try and redeploy the war file (i.e call undeploy then deploy
in
the
ant script) i get the message Cannot remove document base for path
/myapp
Why does 4.1.27 unpack its war files into the web app folder unlike
4.1.18?
I've tried replacing the server.xml file with the one from 4.1.18 but
it
still does the same thing. Is there a setting that I need to make
4.1.27
behave in the same way as 4.1.18?
Thanks
Tom
Limehouse Court, 3-11 Dod Street
London E14 7EQ Tel: 020 7537 8515
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential
business communication, and may contain information that is
confidential, proprietary and/or privileged. This e-mail is
intended only for the individual(s) to whom it is addressed, and
may not be saved, copied, printed, disclosed or used by anyone
else. If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and
notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Manager app in 4.1.27 behaves differently to 4.1.18
I believe the point that Yoav was going to make was that Tomcat 4.1.18 doesn't honor the unpackWARs Host setting when using the Manager's deploy function. Thus it always serves such a webapp from the WAR, for which the Manager undeploy works. Tomcat 4.1.27 does honor the unpackWARs setting, so the same deploy command results in an auto-expanded webapp, if unpackWARs=true. I believe the Manager undeploy command in both 4.1.18 and 4.1.27 has trouble removing an auto-expanded WAR. If you set unpackWARs=false in 4.1.27, you would get the same behavior with respect to deploying and undeploying that you saw in Tomcat 4.1.18. Cheers, Larry -Original Message- From: Tom Lyle [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 10:18 AM To: Tomcat Users List Subject: RE: Manager app in 4.1.27 behaves differently to 4.1.18 Hi, I've reduced my server.xml down to the bare minumum of ROOT, manager admin contexts I use a copy of the same server.xml in an instance of Tomcat 4.1.27 Tomcat 4.1.18 and use the org.apache.catalina.ant.DeployTask to deploy my war file. In 4.1.18 it unpacks it into \work\localhost\myapp in 4.1.27 it unpacks it into \webapps\myapp (it also creates an empty myapp dir in \work\localhost ) in 4.1.27 the UndeployTask will not work because it can't remove the myapp dir in the webapp directory. The server.xml i used in both cases is attached bellow I'm totally at a loss as to whats going on Tom ?xml version='1.0' encoding='utf-8'? Server className=org.apache.catalina.core.StandardServer debug=0 port=8005 shutdown=SHUTDOWN Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycle Listener debug=0/ GlobalNamingResources Environment name=simpleValue override=true type=java.lang.Integer value=30/ Resource auth=Container description=User database that can be updated and saved name=UserDatabase scope=Shareable type=org.apache.catalina.UserDatabase/ ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources Service className=org.apache.catalina.core.StandardService debug=0 name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=100 bufferSize=2048 connectionTimeout=2 debug=9 disableUploadTimeout=true enableLookups=true maxProcessors=75 minProcessors=5 port=8080 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=10 bufferSize=2048 connectionTimeout=2 debug=0 disableUploadTimeout=false enableLookups=true maxProcessors=75 minProcessors=5 port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone Host className=org.apache.catalina.core.StandardHost appBase=webapps autoDeploy=true configClass=org.apache.catalina.startup.ContextConfig contextClass=org.apache.catalina.core.StandardContext debug=0 deployXML=true errorReportValveClass=org.apache.catalina.valves.ErrorReportValve liveDeploy=true mapperClass=org.apache.catalina.core.StandardHostMapper name=localhost unpackWARs=true Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=0 displayName=Tomcat Administration Application docBase=../server/webapps/admin mapperClass=org.apache.catalina.core.StandardContextMapper path=/admin privileged=true reloadable=false swallowOutput=false useNaming=true wrapperClass=org.apache.catalina.core.StandardWrapper Logger className=org.apache.catalina.logger.FileLogger debug=0 directory=logs prefix=localhost_admin_log. suffix=.txt timestamp=true verbosity=1/ /Context Context className=org.apache.catalina.core.StandardContext cachingAllowed=true charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true crossContext=false debug=0 displayName=Welcome to Tomcat docBase=C:\jakarta-tomcat-4.1.27\webapps\ROOT mapperClass
