tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jacky" <jacky_ch...@hotmail.com>
Subject Re: Re: context error
Date Thu, 16 Feb 2006 02:12:00 GMT
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" <jacky_chenp@hotmail.com>
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="20000"
>                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 on port 8081 -->
>     <!-- See proxy documentation for more information about using this. -->
>     <!--
>     <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
>                port="8081" minProcessors="5" maxProcessors="75"
>                enableLookups="true"
>                acceptCount="100" debug="0" connectionTimeout="20000"
>                proxyPort="80" useURIValidationHack="false"
>                disableUploadTimeout="true" />
>     -->
> 
>     <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -->
>     <!--
>     <Connector className="org.apache.catalina.connector.http10.HttpConnector"
>                port="8082" minProcessors="5" maxProcessors="75"
>                enableLookups="true" redirectPort="8443"
>                acceptCount="10" debug="0"/>
>     -->
> 
>     <!-- An Engine represents the entry point (within Catalina) that processes
>          every request.  The Engine implementation for Tomcat stand alone
>          analyzes the HTTP headers included with the request, and passes them
>          on to the appropriate Host (virtual host). -->
> 
>     <!-- Define the top level container in our container hierarchy -->
>     <Engine name="Standalone" defaultHost="localhost" debug="0">
> 
>       <!-- The request dumper valve dumps useful debugging information about
>            the request headers and cookies that were received, and the response
>            headers and cookies that were sent, for all requests received by
>            this instance of Tomcat.  If you care only about requests to a
>            particular virtual host, or a particular application, nest this
>            element inside the corresponding <Host> or <Context> entry instead.
> 
>            For a similar mechanism that is portable to all Servlet 2.3
>            containers, check out the "RequestDumperFilter" Filter in the
>            example application (the source for this filter may be found in
>            "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
> 
>            Request dumping is disabled by default.  Uncomment the following
>            element to enable it. -->
>       <!--
>       <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
>       -->
> 
>       <!-- Global logger unless overridden at lower levels -->
>       <Logger className="org.apache.catalina.logger.FileLogger"
>               prefix="catalina_log." suffix=".txt"
>               timestamp="true"/>
> 
>       <!-- Because this Realm is here, an instance will be shared globally -->
> 
>       <Realm className="org.apache.catalina.realm.MemoryRealm" />
> 
>       <!-- Replace the above Realm with one of the following to get a Realm
>            stored in a database and accessed via JDBC -->
> 
>       <!--
>       <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
>              driverName="org.gjt.mm.mysql.Driver"
>           connectionURL="jdbc:mysql://localhost/authority"
>          connectionName="test" connectionPassword="test"
>               userTable="users" userNameCol="user_name" userCredCol="user_pass"
>           userRoleTable="user_roles" roleNameCol="role_name" />
>       -->
> 
>       <!--
>       <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
>              driverName="oracle.jdbc.driver.OracleDriver"
>           connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
>          connectionName="scott" connectionPassword="tiger"
>               userTable="users" userNameCol="user_name" userCredCol="user_pass"
>           userRoleTable="user_roles" roleNameCol="role_name" />
>       -->
> 
>       <!--
>       <Realm  className="org.apache.catalina.realm.JDBCRealm" debug="99"
>              driverName="sun.jdbc.odbc.JdbcOdbcDriver"
>           connectionURL="jdbc:odbc:CATALINA"
>               userTable="users" userNameCol="user_name" userCredCol="user_pass"
>           userRoleTable="user_roles" roleNameCol="role_name" />
>       -->
> 
>       <!-- Define the default virtual host -->
>       <Host name="localhost" debug="0" appBase="webapps" 
>        unpackWARs="true" autoDeploy="true">
> 
>         <!-- Normally, users must authenticate themselves to each web app
>              individually.  Uncomment the following entry if you would like
>              a user to be authenticated the first time they encounter a
>              resource protected by a security constraint, and then have that
>              user identity maintained across *all* web applications contained
>              in this virtual host. -->
>         <!--
>         <Valve className="org.apache.catalina.authenticator.SingleSignOn"
>                    debug="0"/>
>         -->
> 
>         <!-- Access log processes all requests for this virtual host.  By
>              default, log files are created in the "logs" directory relative to
>              $CATALINA_HOME.  If you wish, you can specify a different
>              directory with the "directory" attribute.  Specify either a relative
>              (to $CATALINA_HOME) or absolute path to the desired directory.
>         -->
>         <Valve className="org.apache.catalina.valves.AccessLogValve"
>                  directory="logs"  prefix="localhost_access_log." suffix=".txt"
>                  pattern="common"/>
> 
>         <!-- Logger shared by all Contexts related to this virtual host.  By
>              default (when using FileLogger), log files are created in the "logs"
>              directory relative to $CATALINA_HOME.  If you wish, you can specify
>              a different directory with the "directory" attribute.  Specify either a
>              relative (to $CATALINA_HOME) or absolute path to the desired
>              directory.-->
>         <Logger className="org.apache.catalina.logger.FileLogger"
>                  directory="logs"  prefix="localhost_log." suffix=".txt"
>          timestamp="true"/>
> 
>         <!-- Define properties for each web application.  This is only needed
>              if you want to set non-default properties, or have web 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" <wapace@bellsouth.net>
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Sent: Wednesday, February 15, 2006 6:42 PM
> Subject: Re: Re: context error
> 
> 
> > 
> > > 
> > > From: "jacky" <jacky_chenp@hotmail.com>
> > > Date: 2006/02/14 Tue PM 08:32:56 EST
> > > To: "Tomcat Users List" <users@tomcat.apache.org>, 
> > > <mike.sabroff@cygnusb2b.com>
> > > 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: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> > 
> >
Mime
View raw message