Hi,
Refer to the attached Readme.txt file and verify that you have done these
steps.
I think it should solve your problem.
Have also attached the server.xml web.xml files which worked fine for us.
let me know whether ur problem gets solved by this.
-Original Message-
From: Stuart Lewis [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 24, 2005 4:16 PM
To: tomcat-user@jakarta.apache.org
Subject: Configuring dbcp in / ROOT context (tomcat 5.5.7)
Hi,
I've searched the archives and generally on google, and whilst people
see the problem a lot, I've not found a definitive answer for how to
configure dbcp in the root context.
E.g.
In server.xml I have:
Context path=/DBTest docBase=DBTest debug=5 reloadable=true
crossContext=true
Resource name=jdbc/postgres auth=Container type=javax.sql.DataSource
maxActive=100 maxIdle=30 maxWait=1
username=whatver password=whatver
driverClassName=org.postgresql.Driver
url=jdbc:postgresql://127.0.0.1:5432/whatever scope=Shareable
factory=org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory/
/Context
If I copy this, and have it the same, except:
Context path=/ docBase=ROOT debug=5 reloadable=true
crossContext=true
then it fails, with:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC
driver of class '' for connect URL 'null'
How should I be configuring my postgress connection for use in the root
context?
Any help will be hugely appreciated, and will stop me from pulling any
more of my hair out!
Thanks,
Stuart
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_
This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at [EMAIL PROTECTED] and delete this mail.
_
!-- 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
!-- 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
namefactory/name
valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value
/parameter
parameter
namepathname/name
valueconf/tomcat-users.xml/value
/parameter
/ResourceParams
!-- Defining the DataSource to be used for Tomcat connectionPooling --
/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=Catalina