Thank you - very helpful & much appreciated.
On Sat, Aug 14, 2021 at 4:24 PM Mark Thomas wrote:
> On 14/08/2021 01:51, Andrew Tanton wrote:
> > In the Tomcat "JNDI Datasource How-To" documentation page
> > <
> http://tomcat.apache.org/tomcat-9.0-doc/
On 14/08/2021 01:51, Andrew Tanton wrote:
In the Tomcat "JNDI Datasource How-To" documentation page
<http://tomcat.apache.org/tomcat-9.0-doc/jndi-datasource-examples-howto.html#comments_section>,
there is an unusually opinionated section, which discusses the Java service
provider
In the Tomcat "JNDI Datasource How-To" documentation page
<http://tomcat.apache.org/tomcat-9.0-doc/jndi-datasource-examples-howto.html#comments_section>,
there is an unusually opinionated section, which discusses the Java service
provider (driver manager) mechanism:
"*Howeve
On 2/6/2014 10:45 PM, Filip Hanik wrote:
Yes, define the connection pool in server.xml, GlobalNamingResources then
in context.xml define a ContextLink That binds the shared connection pool
to each context.
Thank you, that worked perfectly. Although I think you meant
ResourceLink.
-Dave
I have defined a JNDI JDBC datasource as a resource in the global
context.xml file. I was under the impression that what this does is to
create a shared connection pool that is tomcat wide. But in practice what
seems to happen is that a new instance of that connection pool is created
for each
Yes, define the connection pool in server.xml, GlobalNamingResources then
in context.xml define a ContextLink That binds the shared connection pool
to each context.
On Thursday, February 6, 2014, David Newman dnew...@unixmonkeys.com wrote:
I have defined a JNDI JDBC datasource as a resource
. We are stuck in the past
like a Simon and Simon re-run...
Tom
-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2008 10:19 AM
To: Tomcat Users List
Subject: Re: Tomcat JNDI datasource
Just had a brainstorm while responding on another post.
The docs
I have an application in Tomcat 5.0.30 that we are trying to get to use
JDBC through JNDI.
I am trying to follow along with
akarta-tomcat-5.0.30/webapps/tomcat-docs/jndi-datasource-examples-howto.
html.
I have setup the context.xml
Context debug=4
Hi
try this
InitialContext ic = new InitialContext();
DataSource ODS = (javax.sql.DataSource)
ic.lookup(java:comp/env/jdbc/medical);
Connection conn = ODS.getConnection();
It works for me in Oracle 10G on TC
with regards
Karthik
I have an application in Tomcat 5.0.30 that we are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom,
Tom Henricksen wrote:
| org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver
| of class '' for connect URL 'null'
Aah, yes. The old connect URL 'null' problem. This is always a problem
with some nitpicky detail in your
Your root cause seems to indicate it's having some trouble possibly with
the url:
Caused by: java.lang.NullPointerException
at java.util.StringTokenizer.init(StringTokenizer.java:146)
at com.ibm.db2.jcc.DB2Driver.acceptsURL(DB2Driver.java:245)
at
Hi. Did you try putting your .jar files in \WEB-INF\lib of you webapp?
Tom Henricksen [EMAIL PROTECTED] 3/28/2008 8:08 AM
I have an application in Tomcat 5.0.30 that we are trying to get to use
JDBC through JNDI.
I am trying to follow along with
| Context debug=4
| docBase=C:/Java/eclipse-europa/europa-workspace/bop-med/web
| path=/bop-med reloadable=true
| workDir=work\Catalina\localhost\bop-med
Bad boy: take out the docBase and path attributes. At best, they will be
ignored. At worse, they will confuse both you /and/
Bad suggestion. It should exist in one and only one place. That place
is common/lib for tc 5.0, 5.5 so it's visible to both tomcat's internal
code and the webapp.
--David
Howard Watson wrote:
Hi. Did you try putting your .jar files in \WEB-INF\lib of you webapp?
Tom Henricksen [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Smith wrote:
|
| | Context debug=4
| | docBase=C:/Java/eclipse-europa/europa-workspace/bop-med/web
| | path=/bop-med reloadable=true
| | workDir=work\Catalina\localhost\bop-med
|
| Bad boy: take out the docBase and path
If the app still had errors with the .jar file in the webapps own \WEB-INF\lib
then something else is broken (called a test). Since his webapp docBase is
outside the Tomcat directory structure there is merit with having associated
.jar files in that docBase. And in instances where there are
It does have merit to keep associated jars together except in those rare
occasions where the jar has to be in the classloader heirarchy at a
place visible to both tomcat's internal code and the webapp's. In that
case it has to be in common/lib and not in any descendant classloader.
To do
Just had a brainstorm while responding on another post.
The docs for 5.0.30 should describe defining a resource in terms of a
Resource ... / element and a ResourceParams/ResourceParams
element. The resource as setup below is only correct for version 5.5.x
and later.
--David
Tom
18 matches
Mail list logo