You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Robert Charbonneau <to...@kdesktop.org> on 2003/08/27 13:56:00 UTC
I was trying to setup Tomcat to allow Apache to serve *.jsp files from the
DocumentRoot of Apache. I had setup the following:
<!-- Example Server 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">
<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
modJk="/www-tomcat/modules/mod_jk.so" />
<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
including your own mbean-descriptor file(s), and setting the
"descriptors" attribute to point to a ';' seperated list of paths
(in the ClassLoader sense) of files to add to the default list.
e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
-->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- 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 -1 -->
<!-- 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 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false"
disableUploadTimeout="true" />
-->
<!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" 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). -->
<!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0"
jmvRoute="jvm1">
-->
<!-- 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 -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<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">
<Listener className="org.apache.ajp.tomcat4.config.ApacheConfig"
append="true" forwardAll="false" modJk="/www-tomcat/modules/mod_jk.so" />
<!-- 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" resolveHosts="false"/>
-->
<!-- 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"/>
-->
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
<!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
<!-- PersistentManager: Uncomment the section below to test
Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 or 0 means unlimited sessions are allowed.
If it is not possible to swap sessions new sessions will
be rejected.
This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
activity.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in
seconds),
and all sessions found in the Store will be loaded on
startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions,
maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then
restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>url</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
<Context path="/" docBase="/jsps/global/root" debug="9"
reloadable="true" >
<Loader checkInterval="3"/>
<Logger className="org.apache.catalina.logger.SystemOutLogger"
timestamp="true"/>
</Context>
</Host>
</Engine>
</Service>
</Server>
I'm wondering if anyone can give me any insight as to how I can make this work
properly.
Thanks.
--
Robert Charbonneau
tomcat-user@kdesktop.org
--
Re:
Posted by Andoni <an...@indigo.ie>.
1. Back up the file.
2. Delete all the comments.
3. Put all single-line XML tags on a single line (even if this means you
can't see the end of some of them)
4. Delete any contexts you don't need (e.g. examples)
5. Then try to work with the file. Or post it to this list and ask your
questions.
As for getting Apache to work with a .jsp file instead of passing it on to
Tomcat all you have to do is remove the
JkMount /*.jsp ajp13
statement from Apache's httpd.conf file. But then these will be treated as
ordinary text files not script files which have to be interpreted.
Andoni.
----- Original Message -----
From: "Robert Charbonneau" <to...@kdesktop.org>
To: "Tomcat Users Mailing List" <to...@jakarta.apache.org>
Sent: Wednesday, August 27, 2003 12:56 PM
Subject: <Context>
> I was trying to setup Tomcat to allow Apache to serve *.jsp files from the
> DocumentRoot of Apache. I had setup the following:
>
>
>
> I'm wondering if anyone can give me any insight as to how I can make this
work
> properly.
>
> Thanks.
>
> --
> Robert Charbonneau
> tomcat-user@kdesktop.org
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
Re:
Posted by Andoni <an...@indigo.ie>.
Hi.
I had that error, that I could not put a .jsp in the root. I am not sure
why but I remember I could not find a way around it at the time so I ended
up putting it in the /jsp folder with all the rest of the .jsp files and
pointing the
<welcome-file-list>
option in web.xml at /jsp/index.jsp
I would try doing some poking around in TOMCAT_HOME/conf/web.xml to see if
there is something getting in the way there.
If you still have problems let me know.
Andoni.
----- Original Message -----
From: "Robert Charbonneau" <to...@kdesktop.org>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Wednesday, August 27, 2003 9:31 PM
Subject: Re: <Context>
> On August 27, 2003 10:12 am, John Turner wrote:
> > Sure, as soon as you give us insight such as:
> >
> > - what's wrong, exactly
>
> I want to be able to run JSPs directly from the root of the domain on the
> webserver. ie. http://domain.tld/index.jsp
>
> When I access http://localhost/index.jsp when the path of the Context
> container is set to "/", I get a 404. This, obviously, is undesirable.
> However, if I simply hit http://localhost/ Apache gives me a directory
> listing which shows me index.jsp.
>
> > - what error messages you're getting
>
> I get a 404 File Not Found error when I try to access index.jsp from /
when
> <Context path="/"
>
> > - what version of Tomcat
>
> 4.1.27
>
> > - what version of Apache, what connector
>
> Apache httpd 2.0.47 and mod_jk-2.0.43.so
>
> > - whether its working in Tomcat standalone, without Apache
>
> It's not working as the root of the tomcat server on port 8080, but I
wasn't
> expecting it to. I want the root of the domain being able to serve JSPs
and
> Servlets so I don't have to create a subdirectory off of the root for this
> purpose.
>
> > - what URL you are trying to use
>
> http://localhost/index.jsp
>
> > Specific information is best. Saying "it doesn't work" doesn't help us
> > help you. Also, there is more involved in Apache + Tomcat than just
> > server.xml, so you will need to give us that information as well (please
> > don't post entire files...just snippets showing deviations from defaults
> > is sufficient).
>
> Sorry about that, most mailing lists I belong to are pretty free form.
I'll
> keep an eye on the amount of data sent in the future.
>
> As for the rest of the configuration, everything is default except
server.xml.
> When I startup Tomcat mod_jk.conf is generated in
$CATALINA_HOME/conf/auto/
> and is included by httpd.conf which is the only modification to that file
I
> made aside from changing ServerName to ServerName localhost.
>
> Any help would be appreciated.
>
> > John
> >
> > Robert Charbonneau wrote:
> > > I was trying to setup Tomcat to allow Apache to serve *.jsp files from
> > > the DocumentRoot of Apache. I had setup the following:
> > >
> > >
> > > <Context path="/" docBase="/jsps/global/root" debug="9"
> > > reloadable="true" >
> > > <Loader checkInterval="3"/>
> > > <Logger
className="org.apache.catalina.logger.SystemOutLogger"
> > > timestamp="true"/>
> > > </Context>
> > >
> > > </Host>
> > >
> > > </Engine>
> > >
> > > </Service>
> > >
> > > </Server>
> > >
> > >
>
> --
> Robert Charbonneau
> tomcat-user@kdesktop.org
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
Re:
Posted by Robin <ro...@portrade.com>.
Robert Charbonneau wrote:
>On August 27, 2003 10:12 am, John Turner wrote:
>
>
>>Sure, as soon as you give us insight such as:
>>
>>- what's wrong, exactly
>>
>>
>
>I want to be able to run JSPs directly from the root of the domain on the
>webserver. ie. http://domain.tld/index.jsp
>
>When I access http://localhost/index.jsp when the path of the Context
>container is set to "/", I get a 404. This, obviously, is undesirable.
>However, if I simply hit http://localhost/ Apache gives me a directory
>listing which shows me index.jsp.
>
>
>
>>- what error messages you're getting
>>
>>
>
>I get a 404 File Not Found error when I try to access index.jsp from / when
><Context path="/"
>
>
>
>>- what version of Tomcat
>>
>>
>
>4.1.27
>
>
>
>>- what version of Apache, what connector
>>
>>
>
>Apache httpd 2.0.47 and mod_jk-2.0.43.so
>
>
>
>>- whether its working in Tomcat standalone, without Apache
>>
>>
>
>It's not working as the root of the tomcat server on port 8080, but I wasn't
>expecting it to. I want the root of the domain being able to serve JSPs and
>Servlets so I don't have to create a subdirectory off of the root for this
>purpose.
>
>
>
>>- what URL you are trying to use
>>
>>
>
>http://localhost/index.jsp
>
>
>
>>Specific information is best. Saying "it doesn't work" doesn't help us
>>help you. Also, there is more involved in Apache + Tomcat than just
>>server.xml, so you will need to give us that information as well (please
>>don't post entire files...just snippets showing deviations from defaults
>>is sufficient).
>>
>>
>
>Sorry about that, most mailing lists I belong to are pretty free form. I'll
>keep an eye on the amount of data sent in the future.
>
>As for the rest of the configuration, everything is default except server.xml.
>When I startup Tomcat mod_jk.conf is generated in $CATALINA_HOME/conf/auto/
>and is included by httpd.conf which is the only modification to that file I
>made aside from changing ServerName to ServerName localhost.
>
>Any help would be appreciated.
>
>
>
>>John
>>
>>Robert Charbonneau wrote:
>>
>>
>>>I was trying to setup Tomcat to allow Apache to serve *.jsp files from
>>>the DocumentRoot of Apache. I had setup the following:
>>>
>>>
>>> <Context path="/" docBase="/jsps/global/root" debug="9"
>>>reloadable="true" >
>>> <Loader checkInterval="3"/>
>>> <Logger className="org.apache.catalina.logger.SystemOutLogger"
>>>timestamp="true"/>
>>> </Context>
>>>
>>> </Host>
>>>
>>> </Engine>
>>>
>>> </Service>
>>>
>>></Server>
>>>
>>>
>>>
>>>
>
>--
>Robert Charbonneau
>tomcat-user@kdesktop.org
>--
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
can you post up worker.properties files? (or worker2.properties)
Re:
Posted by John Turner <to...@johnturner.com>.
Robert Charbonneau wrote:
> It's not working as the root of the tomcat server on port 8080, but I wasn't
> expecting it to. I want the root of the domain being able to serve JSPs and
> Servlets so I don't have to create a subdirectory off of the root for this
> purpose.
That won't work. You must create a subdirectory. All webapps live in
directories, that's just how it works.
The root context looks like this:
<Context path="" docBase="someDir">
</Context>
Here's how I do it (YMMV).
URL= http://some.domain.com
<Host name="some.domain.com" appBase="some.domain.com">
<Context path="" docBase="some.domain.com">
....
</Context>
</Host>
Then index.jsp goes in $CATALINA_HOME/some.host.com/some.host.com. A
little redundant, but for me it is a good reminder. So you end up with:
$CATALINA_HOME
$CATALINA_HOME/some.domain.com
$CATALINA_HOME/some.domain.com/some.domain.com
$CATALINA_HOME/some.domain.com/some.domain.com/index.jsp
$CATALINA_HOME/some.domain.com/some.domain.com/WEB-INF
$CATALINA_HOME/some.domain.com/some.domain.com/WEB-INF/web.xml
$CATALINA_HOME/some.domain.com/some.domain.com/WEB-INF/classes
$CATALINA_HOME/some.domain.com/some.domain.com/WEB-INF/lib
This lets other webapps in the same Host node be subdirs without
confusing things.
As shown in server.xml, you can also follow the convention of naming the
docBase of the root webapp "ROOT", in which case index.jsp would go in
$CATALINA_HOME/some.domain.com/ROOT and you would have something like:
$CATALINA_HOME
$CATALINA_HOME/some.domain.com
$CATALINA_HOME/some.domain.com/ROOT
$CATALINA_HOME/some.domain.com/ROOT/index.jsp
$CATALINA_HOME/some.domain.com/ROOT/WEB-INF
$CATALINA_HOME/some.domain.com/ROOT/WEB-INF/web.xml
$CATALINA_HOME/some.domain.com/ROOT/WEB-INF/classes
$CATALINA_HOME/some.domain.com/ROOT/WEB-INF/lib
Remember that the actual directory name is transparent to the user...the
only person who will ever know that something is in a subdir is the
administrator. Users can still get to http://some.domain.com/whatever.jsp.
Once you have that set up, you can add <welcome-file></welcome-file> to
your web.xml file and set it to index.jsp, and turn off directory
listings as well.
Also try path="", not path="/" for your Context.
> Sorry about that, most mailing lists I belong to are pretty free form. I'll
> keep an eye on the amount of data sent in the future.
We're pretty casual here as well...we just see the same files posted
over and over (server.xml, httpd.conf, etc), so scrolling through 200
lines that aren't changed from the default and checking every line to
see if its the same as the default or not is pretty tedious.
John
Re:
Posted by Robert Charbonneau <to...@kdesktop.org>.
On August 27, 2003 10:12 am, John Turner wrote:
> Sure, as soon as you give us insight such as:
>
> - what's wrong, exactly
I want to be able to run JSPs directly from the root of the domain on the
webserver. ie. http://domain.tld/index.jsp
When I access http://localhost/index.jsp when the path of the Context
container is set to "/", I get a 404. This, obviously, is undesirable.
However, if I simply hit http://localhost/ Apache gives me a directory
listing which shows me index.jsp.
> - what error messages you're getting
I get a 404 File Not Found error when I try to access index.jsp from / when
<Context path="/"
> - what version of Tomcat
4.1.27
> - what version of Apache, what connector
Apache httpd 2.0.47 and mod_jk-2.0.43.so
> - whether its working in Tomcat standalone, without Apache
It's not working as the root of the tomcat server on port 8080, but I wasn't
expecting it to. I want the root of the domain being able to serve JSPs and
Servlets so I don't have to create a subdirectory off of the root for this
purpose.
> - what URL you are trying to use
http://localhost/index.jsp
> Specific information is best. Saying "it doesn't work" doesn't help us
> help you. Also, there is more involved in Apache + Tomcat than just
> server.xml, so you will need to give us that information as well (please
> don't post entire files...just snippets showing deviations from defaults
> is sufficient).
Sorry about that, most mailing lists I belong to are pretty free form. I'll
keep an eye on the amount of data sent in the future.
As for the rest of the configuration, everything is default except server.xml.
When I startup Tomcat mod_jk.conf is generated in $CATALINA_HOME/conf/auto/
and is included by httpd.conf which is the only modification to that file I
made aside from changing ServerName to ServerName localhost.
Any help would be appreciated.
> John
>
> Robert Charbonneau wrote:
> > I was trying to setup Tomcat to allow Apache to serve *.jsp files from
> > the DocumentRoot of Apache. I had setup the following:
> >
> >
> > <Context path="/" docBase="/jsps/global/root" debug="9"
> > reloadable="true" >
> > <Loader checkInterval="3"/>
> > <Logger className="org.apache.catalina.logger.SystemOutLogger"
> > timestamp="true"/>
> > </Context>
> >
> > </Host>
> >
> > </Engine>
> >
> > </Service>
> >
> > </Server>
> >
> >
--
Robert Charbonneau
tomcat-user@kdesktop.org
--
Re:
Posted by John Turner <to...@johnturner.com>.
Sure, as soon as you give us insight such as:
- what's wrong, exactly
- what error messages you're getting
- what version of Tomcat
- what version of Apache, what connector
- whether its working in Tomcat standalone, without Apache
- what URL you are trying to use
Specific information is best. Saying "it doesn't work" doesn't help us
help you. Also, there is more involved in Apache + Tomcat than just
server.xml, so you will need to give us that information as well (please
don't post entire files...just snippets showing deviations from defaults
is sufficient).
John
Robert Charbonneau wrote:
> I was trying to setup Tomcat to allow Apache to serve *.jsp files from the
> DocumentRoot of Apache. I had setup the following:
>
>
> <Context path="/" docBase="/jsps/global/root" debug="9"
> reloadable="true" >
> <Loader checkInterval="3"/>
> <Logger className="org.apache.catalina.logger.SystemOutLogger"
> timestamp="true"/>
> </Context>
>
> </Host>
>
> </Engine>
>
> </Service>
>
> </Server>
>
>
> I'm wondering if anyone can give me any insight as to how I can make this work
> properly.
>
> Thanks.
>
> --
> Robert Charbonneau
> tomcat-user@kdesktop.org
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>