Tim,
On 8/31/23 04:03, Scott,Tim wrote:
Hi Chris,
Hi all,
Thanks for your responses. I think I've found the problem.
My wrapping class which detects the invocation of the close() method to
decrement its count is no longer decrementing its count because
method.getDeclaringClass() has
Hi Chris,
> > Hi all,
> >
> > Thanks for your responses. I think I've found the problem.
> >
> > My wrapping class which detects the invocation of the close() method to
> > decrement its count is no longer decrementing its count because
> > method.getDeclaringClass() has changed from
Tim,
On 8/29/23 10:33, Scott,Tim wrote:
Hi all,
Thanks for your responses. I think I've found the problem.
My wrapping class which detects the invocation of the close() method to
decrement its count is no longer decrementing its count because
method.getDeclaringClass() has changed from
Hi all,
Thanks for your responses. I think I've found the problem.
My wrapping class which detects the invocation of the close() method to
decrement its count is no longer decrementing its count because
method.getDeclaringClass() has changed from java.sql.Connection to
Tim,
On 8/25/23 10:48, Scott,Tim wrote:
Hi John,
Why does your app need 20 connections just to start up? That's a
bit of a rhetorical question, but needing so many connections to
start up seems odd to me.
It doesn't. It only needs 1-2 at a time, but it makes 100s of queries
in loops, each
Hi John,
> Why does your app need 20 connections just to start up? That's a bit of a
> rhetorical question, but needing so many connections to start up seems odd to
> me.
It doesn't. It only needs 1-2 at a time, but it makes 100s of queries
in loops, each time using a connection from
Tim,
> -Original Message-
> From: Scott,Tim
> Sent: Friday, August 25, 2023 3:09 AM
> To: users@tomcat.apache.org
> Subject: DataSource Connection pool leak
>
> Hi,
>
> For various diagnostics, I tried Tomcat 9.0.79 recently on a development
> machine.
Hi,
For various diagnostics, I tried Tomcat 9.0.79 recently on a development
machine. It didn't solve the problem I was experiencing - that was later
identified as a problem in IntelliJ with remote deployment and is not why I'm
mailing.
I tweaked my Tomcat 9.0.79 configuration to start my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rajendra
On 3/18/19 12:24, Rajendra wrote:
> Tomcat(8.5.32) is not establishing connections to database after
> database is restarted. Currently, I am restarting Tomcat instance
> if DB is restarted. Please let me know any parameters need to be
>
Hello Rajendra,
For instance if you are using MYSQL a validationQuery="l" in your
datasource configuration [1] plus the magic autoreconnect parameter in the
URL can do the trick for you. However this can have side effects (see the
mysql autoreconnect description).
In my experience the cheapest
Hi,
Tomcat(8.5.32) is not establishing connections to database after database is
restarted. Currently, I am restarting Tomcat instance if DB is restarted.
Please let me know any parameters need to be added to datasource resource
element in Tomcat in order to establish database connections
Hello.
i've not access to Tomcat's server.xml where the sysadmins defined a resource:
Resource driverClassName=oracle.jdbc.driver.OracleDriver
maxActive=65 maxIdle=30 maxWait=5 name=myDatasource
type=javax.sql.DataSource url=jdbc:. /
I wish to discover from a web appplication deployed on
(Config.getParamAsBoolean(pool.test.on.return));
tds.setTestWhileIdle(Config.getParamAsBoolean(pool.test.while.idle));
-Original Message-
From: GF [mailto:gan...@gmail.com]
Sent: 03 November 2010 11:16
To: Tomcat Users List
Subject: Discover the Datasource connection pool maxSize.
Hello.
i've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
GF,
On 11/3/2010 7:15 AM, GF wrote:
i've not access to Tomcat's server.xml where the sysadmins defined a resource:
Resource driverClassName=oracle.jdbc.driver.OracleDriver
maxActive=65 maxIdle=30 maxWait=5 name=myDatasource
On 03/11/2010 12:15, GF wrote:
Hello.
i've not access to Tomcat's server.xml where the sysadmins defined a resource:
Resource driverClassName=oracle.jdbc.driver.OracleDriver
maxActive=65 maxIdle=30 maxWait=5 name=myDatasource
type=javax.sql.DataSource url=jdbc:. /
I wish to discover
Hi
I have sucessfully created a JDBC connection using DataSource and JNDI on
Tomcat5.x
Is it necessary for create a Connection POOL using this DataSource based
Jdbc Connnection
or will the DataSource itself provides the Connection POOL for managing
the JDBC connections
on startup
Hey,
I think though I'm not 100%
When you declare the datasource in web.xml (or is Server.xml?) it creates a
pool factory for you under the covers (I think using Jakarta DBCP). When you
use JNDI look-up it asks the factory for a pool. You are then magically using
a pool. You
enough to handle
all of your db connections. Set to 0 for no limit.
--
Hope this helps,
Regards,
Prathibha.
-Original Message-
From: Karthik [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 4:36 PM
To: TOMCAT
Subject: TOMCAT + DATASOURCE + CONNECTION POOL
18 matches
Mail list logo
