-----Original Message----- From: Craig R. McClanahan [mailto:crai...@apache.org] Sent: Tuesday, October 29, 2002 10:16 PM To: Tomcat Users List Subject: RE: DBCP Woes! Ahaa!

On Tue, 29 Oct 2002, neal wrote:

The crossContext attribute has nothing at all to do with JNDI resources -- it only determines whether the ServletContext.getContext() method will unconditionally return null or not. See the documentation (hyperlink listed below) for more details.

JNDI resources for each <Context> must be configured individually. If you are using Tomcat 4.1, there is a mechanism to share the physical resources themselves (such as a JDBC data source) by defining the resources in the <GlobalNamingResources> section at the top of server.xml, and then using a <ResourceLink> element nested inside each <Context> element that links to it (analogous to a symbolic link in a filesystem).

Are all (or most) of the domain names supposed to resolve to the exact same set of webapps? If so, you're probably best off using the "defaulthost" capability of the <Engine> element:

<Engine name="Standalone" defaulthost="hotel.us"> <Host name="hotel.us" appBase="webapps/hotel"> ... </Host> <Host name="other.com" appBase="..."> ... </Host> </Engine>

In this scenario, any request received by this Tomcat instance, for any unrecognized host name will be forwarded to the hotel.us domain. You can explicitly list the separate hosts that should not be shared, as illustrated with the "other.com" entry above.

For more info about all of the server.xml options, see the docs included in the standard Tomcat distribution at:

http://localhost:8080/tomcat-docs/config/

or online:

http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/ http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/

Craig