Re: Missing Context error text
Eric Dalquist wrote: Is this behavior, writing to the underlying response object, dictated by the spec? Is this required of Tomcat versus writing to the PrintWriter provided by the response wrapper. Not that I can see in the spec. Also, my quick test shows that the DefaultServlet (which creates the missing resource message) calls getWriter() on the wrapped response object as expected. It is possible you are missing a wrapper somewhere? If not, if you create a new bug and attach the simplest test case that demonstrates the issue (two classes: a wrapper and a servlet should be enough) I'll take a closer look. BTW, if you don't like the message, using your own DefaultServlet (eg the Tomcat one less the few lines of code that write the message) would be a way around it. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1 Admin Context Error.
Hi guys, I'm using Tomcat 4.1 currently. I'm facing problem to create a datasource for a context that is created by uploading a .war file. It prints out the following error: javax.servlet.ServletException: Exception retrieving attribute 'driverClassName'I think this should be fixed in Tomcat 5, but unfortunately upgrading Tomcat is not an option for me now. Any workarounds that i can use?Many ThanxThanx. Regards, FooShyn
Re: Re: context error
From: jacky [EMAIL PROTECTED] Date: 2006/02/16 Thu PM 11:08:59 EST To: Tomcat Users List users@tomcat.apache.org Subject: Re: Re: context error I added the Context path= docBase=ROOT debug=0/, it still doesn't work Best Regards. jacky - Original Message - From: Caldarale, Charles R [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Friday, February 17, 2006 10:13 AM Subject: RE: Re: context error From: jacky [EMAIL PROTECTED] Subject: Re: Re: context error server.xml is the default server.xml: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- jacky The !-- and -- you have before and after the default context descriptor are commenting it out. Remove those. I sent you a snippet to try earlier. Any luck? Warren Part of the problem may be that you have no default Context. There should be one (and only one) Context tag with path=. If you want your app to be the default, you can just set its path to . - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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: Re: context error
From: jacky [EMAIL PROTECTED] Date: 2006/02/15 Wed PM 09:00:29 EST To: Tomcat Users List users@tomcat.apache.org Subject: Re: Re: context error hi, RedHat7.3, J2sdk1.4.2_10 server.xml is the default server.xml: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- !--Context path=/myworkflow docBase=myworkflow /-- //here, myworkflow is my web app. Been a while since I used 4.1 - this is from memory. try Context path=/myworkflow docBase=myworkflow reloadable=true crossContext=true /Context /Host /Engine /Service !-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0 as its servlet container. Please read the README.txt file coming with the WebApp Module distribution on how to build it. (Or check out the jakarta-tomcat-connectors/webapp CVS repository) To configure the Apache side, you must ensure that you have the ServerName and Port directives defined in httpd.conf. Then, lines like these to the bottom of your httpd.conf file: LoadModule webapp_module libexec/mod_webapp.so WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples/ The next time you restart Apache (after restarting Tomcat, if needed) the connection will be established, and all applications you make visible via WebAppDeploy directives can be accessed through Apache. -- !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache debug=0 appBase=webapps !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service /Server Best Regards. jacky - Original Message - From: Warren Pace [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, February 15, 2006 6:42 PM Subject: Re: Re: context error From: jacky [EMAIL PROTECTED] Date: 2006/02/14 Tue PM 08:32:56 EST To: Tomcat Users List users@tomcat.apache.org, [EMAIL PROTECTED] Subject: Re: context error hi, Mike, Do you mean put all directories together? No, we need to separate them. So, any other suggestions about this problem? Best Regards. jacky Could you send us your server.xml with and without the added context? I see you're using 4.1. What OS and what JVM are you using? - 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: Re: context error
I added the reloadable=true crossContext=true, but the same errors occur. Best Regards. jacky - Original Message - From: Warren Pace [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Friday, February 17, 2006 5:35 AM Subject: Re: Re: context error From: jacky [EMAIL PROTECTED] Date: 2006/02/15 Wed PM 09:00:29 EST To: Tomcat Users List users@tomcat.apache.org Subject: Re: Re: context error hi, RedHat7.3, J2sdk1.4.2_10 server.xml is the default server.xml: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- !--Context path=/myworkflow docBase=myworkflow /-- //here, myworkflow is my web app. Been a while since I used 4.1 - this is from memory. try Context path=/myworkflow docBase=myworkflow reloadable=true crossContext=true /Context /Host /Engine /Service !-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0 as its servlet container. Please read the README.txt file coming with the WebApp Module distribution on how to build it. (Or check out the jakarta-tomcat-connectors/webapp CVS repository) To configure the Apache side, you must ensure that you have the ServerName and Port directives defined in httpd.conf. Then, lines like these to the bottom of your httpd.conf file: LoadModule webapp_module libexec/mod_webapp.so WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples/ The next time you restart Apache (after restarting Tomcat, if needed) the connection will be established, and all applications you make visible via WebAppDeploy directives can be accessed through Apache. -- !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache debug=0 appBase=webapps !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service /Server Best Regards. jacky - Original Message - From: Warren Pace [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, February 15, 2006 6:42 PM Subject: Re: Re: context error From: jacky [EMAIL PROTECTED] Date: 2006/02/14 Tue PM 08:32:56 EST To: Tomcat Users List users@tomcat.apache.org, [EMAIL PROTECTED] Subject: Re: context error hi, Mike, Do you mean put all directories together? No, we need to separate them. So, any other suggestions about this problem? Best Regards. jacky Could you send us your server.xml with and without the added context? I see you're using 4.1. What OS and what JVM are you using? - 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: Re: context error
From: jacky [EMAIL PROTECTED] Subject: Re: Re: context error server.xml is the default server.xml: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- Part of the problem may be that you have no default Context. There should be one (and only one) Context tag with path=. If you want your app to be the default, you can just set its path to . - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: context error
I added the Context path= docBase=ROOT debug=0/, it still doesn't work Best Regards. jacky - Original Message - From: Caldarale, Charles R [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Friday, February 17, 2006 10:13 AM Subject: RE: Re: context error From: jacky [EMAIL PROTECTED] Subject: Re: Re: context error server.xml is the default server.xml: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- Part of the problem may be that you have no default Context. There should be one (and only one) Context tag with path=. If you want your app to be the default, you can just set its path to . - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: context error
From: jacky [EMAIL PROTECTED] Date: 2006/02/14 Tue PM 08:32:56 EST To: Tomcat Users List users@tomcat.apache.org, [EMAIL PROTECTED] Subject: Re: context error hi, Mike, Do you mean put all directories together? No, we need to separate them. So, any other suggestions about this problem? Best Regards. jacky Could you send us your server.xml with and without the added context? I see you're using 4.1. What OS and what JVM are you using? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: context error
application document roots in places other than the virtual host's appBase directory. -- !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- !--Context path=/myworkflow docBase=myworkflow /-- //here, myworkflow is my web app. /Host /Engine /Service !-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0 as its servlet container. Please read the README.txt file coming with the WebApp Module distribution on how to build it. (Or check out the jakarta-tomcat-connectors/webapp CVS repository) To configure the Apache side, you must ensure that you have the ServerName and Port directives defined in httpd.conf. Then, lines like these to the bottom of your httpd.conf file: LoadModule webapp_module libexec/mod_webapp.so WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples/ The next time you restart Apache (after restarting Tomcat, if needed) the connection will be established, and all applications you make visible via WebAppDeploy directives can be accessed through Apache. -- !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache debug=0 appBase=webapps !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / /Engine /Service /Server Best Regards. jacky - Original Message - From: Warren Pace [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, February 15, 2006 6:42 PM Subject: Re: Re: context error From: jacky [EMAIL PROTECTED] Date: 2006/02/14 Tue PM 08:32:56 EST To: Tomcat Users List users@tomcat.apache.org, [EMAIL PROTECTED] Subject: Re: context error hi, Mike, Do you mean put all directories together? No, we need to separate them. So, any other suggestions about this problem? Best Regards. jacky Could you send us your server.xml with and without the added context? I see you're using 4.1. What OS and what JVM are you using? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: context error
BTW, if i remove the Context path=/myworkflow docBase=myworkflow / from the server.ml, then tomcat can start. but i can't login the manager tool which is http://localhost:8080/manager/html with admin/admin, and still can't access myworkflow by http://localhost:8080/myworkflow/ Best Regards. jacky - Original Message - From: jacky [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Thursday, February 16, 2006 10:00 AM Subject: Re: Re: context error hi, RedHat7.3, J2sdk1.4.2_10 server.xml is the default server.xml: !-- Alternate Example-less Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Uncomment this entry to enable JMX MBeans support -- !-- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0 port=-1 login=admin password=admin/ -- !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Tomcat-Standalone !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 4.0 documentation bundle for more detailed instructions): * Download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to 0 -- !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- !-- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=100 debug=0 scheme=https secure=true useURIValidationHack=false disableUploadTimeout=true Factory className=org.apache.coyote.tomcat4.CoyoteServerSocketFactory clientAuth=false protocol=TLS / /Connector -- !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- !-- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ -- !-- Define an AJP 1.3 Connector on port 8009 -- !-- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ -- !-- Define a Proxied HTTP/1.1 Connector
Re: context error
Then do that jacky wrote: hi, When i add a Context in the server.xml, an error occurs: Apache Tomcat/4.1.31 Catalina.start: LifecycleException: Context startup failed due to previous errors LifecycleException: Context startup failed due to previous errors at org.apache.catalina.core.StandardContext.start(StandardContext.java:3578) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardHost.start(StandardHost.java:707) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) at org.apache.catalina.startup.Catalina.start(Catalina.java:463) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) Stopping service Tomcat-Standalone Catalina.stop: LifecycleException: Coyote connector has not been started LifecycleException: Coyote connector has not been started at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1296) at org.apache.catalina.core.StandardService.stop(StandardService.java:499) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178) at org.apache.catalina.startup.Catalina.start(Catalina.java:494) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) If i remove the added context, tomcat will start. In fact, i rearrange the directories, i don't know if this will impact on the Context. If i put all directories under $CATALINA_HOME, tomcat will work well with the Context. $CATALINA_HOME/bin/ shared/ server/ $CATALINA_BASE/bin/ conf/ webapps/ logs/ work/ Context is as following: Context path=/test docBase=test reloadable=true / Best Regards. jacky -- Mike Sabroff Web Services Developer [EMAIL PROTECTED] 920-568-8379 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: context error
hi, Mike, Do you mean put all directories together? No, we need to separate them. So, any other suggestions about this problem? Best Regards. jacky - Original Message - From: Mike Sabroff [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, February 14, 2006 10:56 PM Subject: Re: context error Then do that jacky wrote: hi, When i add a Context in the server.xml, an error occurs: Apache Tomcat/4.1.31 Catalina.start: LifecycleException: Context startup failed due to previous errors LifecycleException: Context startup failed due to previous errors at org.apache.catalina.core.StandardContext.start(StandardContext.java:3578) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardHost.start(StandardHost.java:707) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) at org.apache.catalina.startup.Catalina.start(Catalina.java:463) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) Stopping service Tomcat-Standalone Catalina.stop: LifecycleException: Coyote connector has not been started LifecycleException: Coyote connector has not been started at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1296) at org.apache.catalina.core.StandardService.stop(StandardService.java:499) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178) at org.apache.catalina.startup.Catalina.start(Catalina.java:494) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) If i remove the added context, tomcat will start. In fact, i rearrange the directories, i don't know if this will impact on the Context. If i put all directories under $CATALINA_HOME, tomcat will work well with the Context. $CATALINA_HOME/bin/ shared/ server/ $CATALINA_BASE/bin/ conf/ webapps/ logs/ work/ Context is as following: Context path=/test docBase=test reloadable=true / Best Regards. jacky -- Mike Sabroff Web Services Developer [EMAIL PROTECTED] 920-568-8379 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
context error
hi, When i add a Context in the server.xml, an error occurs: Apache Tomcat/4.1.31 Catalina.start: LifecycleException: Context startup failed due to previous errors LifecycleException: Context startup failed due to previous errors at org.apache.catalina.core.StandardContext.start(StandardContext.java:3578) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardHost.start(StandardHost.java:707) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) at org.apache.catalina.startup.Catalina.start(Catalina.java:463) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) Stopping service Tomcat-Standalone Catalina.stop: LifecycleException: Coyote connector has not been started LifecycleException: Coyote connector has not been started at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1296) at org.apache.catalina.core.StandardService.stop(StandardService.java:499) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178) at org.apache.catalina.startup.Catalina.start(Catalina.java:494) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) If i remove the added context, tomcat will start. In fact, i rearrange the directories, i don't know if this will impact on the Context. If i put all directories under $CATALINA_HOME, tomcat will work well with the Context. $CATALINA_HOME/bin/ shared/ server/ $CATALINA_BASE/bin/ conf/ webapps/ logs/ work/ Context is as following: Context path=/test docBase=test reloadable=true / Best Regards. jacky
