Good morning Apache team!
It's been a while since I installed tomcat and having some jdbc errors with
version 6.0.20. We don't have a mysql.jdbc.driver and uncertain why its
trying to register this. However we do have the oracle.jdbc.driver and the
connections and driver location are accurate
On 24/01/2014 18:24, Leo Medina wrote:
It's been a while since I installed tomcat and having some jdbc errors with
version 6.0.20.
Time to upgrade.
We don't have a mysql.jdbc.driver
com.mysql.jdbc.Driver must be present in one of your webapps. I'd expect
it to be in a JAR that has mysql
On 22.11.2013, at 02:20, Christopher Schultz ch...@christopherschultz.net
wrote:
I also think that this is a justifiable spec violation, and all I’m
asking is that this fact is shown more prominently, esp. as JDBC
pool is advertised as a drop-in replacement for DBCP.
Fair enough. Care you
and JDBC resources
immediately instead of waiting for them to be automatically
released.
Does that mean that all connection pools by design are in direct
violation of the JDBC spec?
I assume you’re referring to the Releases this Connection object's
database resources” part, then yes
you have here, there are
likely resource issues in other places, too.
Keep reading for some commentary.
On 11/19/13, 8:32 AM, Carl Boberg wrote:
JDBC: I see the weird behaviour and my DBA is angry Resource
name=database1 auth=Container maxActive=50 maxIdle=10
minIdle=2 initialSize=0 username
, (the devs have named it dispose). From my
untrained non java dev eye we do not seem to be doing
statement.Close(); and Im curious if that might be the issue?
If so, why does DBCP handle it nicely and not JDBC?
Commons DBCP tracks Statements and ResultSets when they are
created and closes
On 20.11.2013, at 14:21, Christopher Schultz ch...@christopherschultz.net
wrote:
Rainer,
FWIW, Connection.close also states this:
Releases this Connection object's database and JDBC resources
immediately instead of waiting for them to be automatically released.
Does that mean
Thanks for taking the time Daniel,
It is very hard to explain the problem since, and it was also stupid of me
to not include the fact that I have tried all kinds of similar combinations
of configuration in context.xml. With botch dbcp and jdbc pools
The behaviour persists. For example
it nicely and not JDBC?
Commons DBCP tracks Statements and ResultSets when they are created and
closes the associated Statements and ResultSets when the connection that
created them is returned to the pool.
Tomcat's JDBC pool does not do this. This is one of the reasons that
Commons DBCP has
in context.xml. With botch dbcp and jdbc pools
The behaviour persists. For example these are one version of config. I have
tested.
DBCP: behaviour is absent and all i well
Resource name=database1
auth=Container
maxActive=50
maxIdle=8
minIdle=2
initialSize=0
curious if that might be the issue?
If so, why does DBCP handle it nicely and not JDBC?
Commons DBCP tracks Statements and ResultSets when they are created and
closes the associated Statements and ResultSets when the connection that
created them is returned to the pool.
Tomcat's JDBC pool
Hello,
We have recently migrated from dbcp pool to the newer tomcat-jdbc pool. As
I understand, it is supposed to be almost a drop in replacement for dbcp.
Everything works great except once small thing. Its a bit difficult for me
to explain but our DBA is really annoyed by it...
With the new
On Nov 18, 2013, at 9:48 AM, Carl Boberg carl.bob...@memnonnetworks.com wrote:
Hello,
We have recently migrated from dbcp pool to the newer tomcat-jdbc pool. As
I understand, it is supposed to be almost a drop in replacement for dbcp.
*Almost* is the key word here. It's very similar
);
} finally {
if ( connection != null ) {
try {
connection.close();
} catch ( final SQLException e ) {
// ignore
}
}
}
}
I'm using the tomcat jdbc database pool
SQLException e ) { // ignore } } } }
Don't forget to close your PreparedStatement and ResultSet objects.
Yes, I know that the JDBC spec says that closing the Connection should
close the associated objects (i.e. statement, result set), but in a
pooled situation, sometimes the JDBC specs break down a bit
Has anyone on this list ever set up an Oracle UCP connection to an Oracle RAC
and had it supporting all RAC features, i.e. dead connections, failover, etc.?
My question is configuration oriented so I don't think exact hardware/os/tomcat
revs are important.
However, assume Oracle 11gR2 and either
This has now been resolved. Thanks anyway.
--
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
This is now resolved. Thanks anyway.
-Original Message-
From: app...@dsl.pipex.com [mailto:app...@dsl.pipex.com]
Sent: 06 Aug 2013 00 30
To: users@tomcat.apache.org
Subject: Why does JDBC application logging SQL instructions in Apache Tomcat
lists 545 repeatedly
I'm not sure
On Tue, Aug 6, 2013 at 7:52 AM, Martin O'Shea app...@dsl.pipex.com wrote:
This is now resolved. Thanks anyway.
For the benefit of anybody else that hits this issue, care to explain
how it was resolved?
Thanks
Chris
-
To
Of chris
derham
Sent: 06 Aug 2013 12 20
To: Tomcat Users List
Subject: Re: Why does JDBC application logging SQL instructions in Apache
Tomcat lists 545 repeatedly
On Tue, Aug 6, 2013 at 7:52 AM, Martin O'Shea app...@dsl.pipex.com wrote:
This is now resolved. Thanks anyway.
For the benefit of anybody
From: Daniel Mikusa [mailto:dmik...@gopivotal.com]
Sent: Monday, August 05, 2013 7:56 AM
To: Tomcat Users List
Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
On Aug 4, 2013, at 2:14 PM, mw...@loftware.com wrote:
From: Mark Eggers [mailto:its_toas...@yahoo.com]
Sent
On Aug 4, 2013, at 2:14 PM, mw...@loftware.com wrote:
From: Mark Eggers [mailto:its_toas...@yahoo.com]
Sent: Friday, August 02, 2013 5:28 PM
To: Tomcat Users List
Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
On 8/2/2013 1:30 PM, mw...@loftware.com wrote:
From: Michael
I'm not sure of this is an Apache Tomcat issue or not but here goes: I am
currently running a number of programs in
batch which dynamically create and populate a number of tables in MySQL Server
Version 5.5.
When I do this, I am logging the SQL to an Apache Tomcat log file. Sometimes
the SQL
From: Mark Eggers [mailto:its_toas...@yahoo.com]
Sent: Friday, August 02, 2013 5:28 PM
To: Tomcat Users List
Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
On 8/2/2013 1:30 PM, mw...@loftware.com wrote:
From: Michael-O [mailto:1983-01...@gmx.net] Sent: Friday, August 02
, setting
driverManagerProtection to false in the JreMemoryLeakPreventionListener allows
this to work in 6.0.35 as well. I would not have expected that a change to the
MemoryLeak Listener would have changed the behavior of the JDBC driver.
I don't know the internals of the SQL Server driver, so I
to Bug 51640
is the cause of this, and in fact, setting driverManagerProtection to
false in the JreMemoryLeakPreventionListener allows this to work in
6.0.35 as well. I would not have expected that a change to the
MemoryLeak Listener would have changed the behavior of the JDBC
driver.
I don't know
From: Michael-O [mailto:1983-01...@gmx.net]
Sent: Friday, August 02, 2013 3:28 PM
To: Tomcat Users List
Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
Am 2013-08-02 21:24, schrieb mw...@loftware.com:
I expect that by putting the SQL Server JDBC4 driver jar
(sqljdbc4
On 8/2/2013 1:30 PM, mw...@loftware.com wrote:
From: Michael-O [mailto:1983-01...@gmx.net] Sent: Friday, August
02, 2013 3:28 PM To: Tomcat Users List Subject: Re: Auto-loading of
the SQL Server JDBC Driver in 6.0.35
Am 2013-08-02 21:24, schrieb mw...@loftware.com:
I expect that by putting
because I have set a
QueryTimeout in the JDBC Pool. Mark Thomas noted that this is
likely a bug in the driver. I have taken action and created a
service request with Oracle.
My personal analysis with VisualVM: The thread is spawned when
the first query is run. The thread keeps running when
On May 27, 2013, at 7:40 AM, Huub Sepers h.sep...@portbase.com wrote:
Hi,
We are experiencing some problems while using the tomcat jdbc pool.
Tomcat version: apache-tomcat-7.0.29
Try the latest version. Your's is pretty old.
Pool settings:
Resource name=PilDevDS auth
Hi,
We are experiencing some problems while using the tomcat jdbc pool.
Tomcat version: apache-tomcat-7.0.29
Pool settings:
Resource name=PilDevDS auth=Container type=javax.sql.DataSource
factory=org.apache.tomcat.jdbc.pool.DataSourceFactory
testWhileIdle=true
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 5/22/13 1:42 PM, Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool
with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
I suspect that the DriverManager will always be loaded by the
boot ClassLoader, since the default-dispatch for ClassLoaders
is to chekc the parent first, then check yourself. The
DriverManager is at the top-level (well
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener
and Tomcat's JDBC Pool and OracleTimeoutPollingThread
Thanks for the pedantry: I was in fact ignoring the difference between
the system
the
driver in the container, not the app, so this is rarely a problem.
I don't agree with this. I often see this with JDBC drivers which is why
Tomcat has a pile of code specifically to unpick the mess this creates.
**
I will certainly have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 5/23/13 12:01 PM, Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener
and Tomcat's JDBC Pool and OracleTimeoutPollingThread
While I haven't exactly implemented my own JVM or anything like that,
I have...
I
agree to this point.
Most users put the driver in the container, not the app, so this
is rarely a problem.
I don't agree with this. I often see this with JDBC drivers which
is why Tomcat has a pile of code specifically to unpick the mess
this creates.
They are missing the point: the leak
. At present there is no general way to solve this
problem. The necessary hooks are added in JDK 8.
I'd agree to this point.
Most users put the driver in the container, not the app, so this
is rarely a problem.
I don't agree with this. I often see this with JDBC drivers which
is why Tomcat
always get that.
I don't think that will work because the boot ClassLoader won't be
able to load the JDBC driver's classes, since they are in the
container's ClassLoader. (boot ClassLoader should be set to
CATLAINA_BASE/bin/*.jar while the container's ClassLoader will be set
to CATALINA_BASE/lib
, there is primordial, but that doesn't really count)
ClassLoader so you'll always get that.
I don't think that will work because the boot ClassLoader won't be
able to load the JDBC driver's classes, since they are in the
container's ClassLoader. (boot ClassLoader should be set to
CATLAINA_BASE
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener
and Tomcat's JDBC Pool and OracleTimeoutPollingThread
I suspect that the DriverManager will always be loaded by the boot
ClassLoader, since
: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013 09:28, Michael-O wrote:
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
in the container, not the app, so this is rarely a problem.
I don't agree with this. I often see this with JDBC drivers which is why
Tomcat has a pile of code specifically to unpick the mess this creates.
**
I will certainly have to fill out a bug
Am 2013-05-21 20:38, schrieb Mark Thomas:
Seems like they understood the problem. But I do doubt that this is a
fixed size moemory leak.
I think the point they are trying to make is that it is only the first
instance of the web application to be unloaded that will be pinned in
memory.
On 21/05/2013 19:47, Michael-O wrote:
Am 2013-05-21 20:38, schrieb Mark Thomas:
Seems like they understood the problem. But I do doubt that this is a
fixed size moemory leak.
I think the point they are trying to make is that it is only the first
instance of the web application to be unloaded
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
OracleTimeoutPollingThread because I have set a QueryTimeout in the JDBC Pool.
Mark Thomas noted that this is likely a bug in the driver. I have taken action
On 17/05/2013 09:28, Michael-O wrote:
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
OracleTimeoutPollingThread because I have set a QueryTimeout in the JDBC Pool.
Mark Thomas noted that this is likely a bug
Hi Mark,
thanks again for the detailed answer, details inline.
Gesendet: Freitag, 17. Mai 2013 um 11:36 Uhr
Von: Mark Thomas ma...@apache.org
An: Tomcat Users List users@tomcat.apache.org
Betreff: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC
with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013 09:28, Michael-O wrote:
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
OracleTimeoutPollingThread because I have set
List users@tomcat.apache.org
Betreff: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013 09:28, Michael-O wrote:
Hi folks,
there's now a follow-up on the issue [1].
Recap
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Friday, May 17, 2013 7:26 AM
To: Tomcat Users List
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013 12:31
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Friday, May 17, 2013 7:26 AM
To: Tomcat Users List
Subject: Re: Follow-up: Possible false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013
On 17/05/2013 15:34, Jeffrey Janner wrote:
Michael and Mark - I happened to be reviewing how Oracle handles
QueryTimeout yesterday on an unrelated issue and came across a
passage in the JDBC Developers Guide (11g) that covered this
Monitoring Thread (page E-3). My reading
Am 2013-05-08 19:42, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 1:14 PM, Michael-O wrote:
Christopher,
Am 2013-05-08 13:54, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM,
Hi,
I recently have started using the SlowQueryReport to tackle performance issues.
The log message, unfortunately, does not contain the parameters passed to the
prepared statements. Though AbstractQueryReport receives this information in
protected String report*Query(String query, Object[]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the parameters passed to the prepared statements. Though
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/8/13 8:08 AM, Nick Williams wrote:
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the
Dear Users,
Tomcat 7.0.39.
I have the following configuration in META-INF/context.xml:
?xml version=1.0 encoding=UTF-8?
Context cookies=false path=/ reloadable=true
Resource name=jdbc/template auth=Container
driverClassName=org.postgresql.Driver
factory
On May 8, 2013, at 8:54 AM, Lutischán Ferenc wrote:
Dear Users,
Tomcat 7.0.39.
I have the following configuration in META-INF/context.xml:
?xml version=1.0 encoding=UTF-8?
Context cookies=false path=/ reloadable=true
Resource name=jdbc/template auth=Container
driverClassName
?
Context cookies=false path=/ reloadable=true
Resource name=jdbc/template auth=Container driverClassName=org.postgresql.Driver factory=org.apache.tomcat.jdbc.pool.DataSourceFactory initialSize=2
maxIdle=20 maxActive=20 maxWait=5000 password= type=javax.sql.DataSource url=jdbc:postgresql
Am 2013-05-08 14:08, schrieb Nick Williams:
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message,
Am 2013-05-08 14:38, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/8/13 8:08 AM, Nick Williams wrote:
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O
Christopher,
Am 2013-05-08 13:54, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the SlowQueryReport to tackle
performance issues. The log message, unfortunately, does not
contain the
On May 8, 2013, at 12:08 PM, Michael-O wrote:
Am 2013-05-08 14:38, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/8/13 8:08 AM, Nick Williams wrote:
On May 8, 2013, at 6:54 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/8/13 1:34 PM, Nick Williams wrote:
On May 8, 2013, at 12:08 PM, Michael-O wrote:
Am 2013-05-08 14:38, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Nick,
On 5/8/13 8:08 AM, Nick Williams wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/8/13 1:14 PM, Michael-O wrote:
Christopher,
Am 2013-05-08 13:54, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Michael,
On 5/8/13 3:01 AM, Michael-O wrote:
I recently have started using the
On May 8, 2013, at 12:40 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/8/13 1:34 PM, Nick Williams wrote:
On May 8, 2013, at 12:08 PM, Michael-O wrote:
Am 2013-05-08 14:38, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds in
a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said: The
web application [/...] appears to have started a thread named
[OracleTimeoutPollingThread] but has failed to stop it...
We
On 07/05/2013 09:16, Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds
in a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said:
The web application [/...] appears to have started a thread named
Von: Mark Thomas ma...@apache.org
On 07/05/2013 09:16, Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60
seconds in a JDBC Pool data source (7.0.37). When the app was shut down,
Tomcat said: The web application [/...] appears to have
On 07/05/2013 10:25, Michael-O wrote:
Von: Mark Thomas ma...@apache.org On 07/05/2013 09:16,
Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of
60 seconds in a JDBC Pool data source (7.0.37). When the app was
shut down, Tomcat said: The web
Von: Mark Thomas ma...@apache.org
On 07/05/2013 10:25, Michael-O wrote:
Von: Mark Thomas ma...@apache.org On 07/05/2013 09:16,
Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of
60 seconds in a JDBC Pool data source (7.0.37). When the app
Von: Mark Thomas ma...@apache.org
On 07/05/2013 10:25, Michael-O wrote:
Von: Mark Thomas ma...@apache.org On 07/05/2013 09:16,
Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of
60 seconds in a JDBC Pool data source (7.0.37). When the app
a QueryTimeoutInterceptor with
queryTimeout of 60 seconds in a JDBC Pool data source
(7.0.37). When the app was shut down, Tomcat said: The web
application [/...] appears to have started a thread named
[OracleTimeoutPollingThread] but has failed to stop it...
We are using Oracle 11.2g with 11.2.0.3 JDBC drivers
,
Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with
queryTimeout of 60 seconds in a JDBC Pool data source
(7.0.37). When the app was shut down, Tomcat said: The web
application [/...] appears to have started a thread named
[OracleTimeoutPollingThread] but has failed
:25,
Michael-O wrote:
Von: Mark Thomas ma...@apache.org On 07/05/2013
09:16, Michael-O wrote:
Hi folks,
I recently enabled a QueryTimeoutInterceptor with
queryTimeout of 60 seconds in a JDBC Pool data source
(7.0.37). When the app was shut down, Tomcat said: The
web application
time it is borrowed from the pool. Default:
true
http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html
And all works fine
Now , I want to use JDBC Pool with a new web application deployed on that
Tomcat 6.
So, I consider it as an standalone application, and I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jose,
On 4/29/13 9:30 AM, Jose María Zaragoza wrote:
Now , I want to use JDBC Pool with a new web application deployed
on that Tomcat 6. So, I consider it as an standalone application,
and I use org.apache.tomcat.jdbc.pool.DataSource class ( I
.nabble.com/Fwd-Tomcat-Jdbc-Pool-NumActive-vs-actual-Established-Connections-tp4997798p4997845.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional
2013/4/16 Kiren Pillay kirenpill...@gmail.com
Hi All,
I am using the tomcat-jdpc-pool from within my spring application. I am
noticing a discrepancy between the numActive/numIdle values that the pool
reports versus the actual number of established connections to the
database.
For example,
.
Regards
Kiren
--
View this message in context:
http://tomcat.10.x6.nabble.com/Fwd-Tomcat-Jdbc-Pool-NumActive-vs-actual-Established-Connections-tp4997798p4997849.html
Sent from the Tomcat - User mailing list archive at Nabble.com
:
tomcat-juli-7.0.39.jar tomcat-jdbc-7.0.39.jar
2013-04-16 16:04:38,695 DEBUG super.odbc: active:0 idle: 4 max:50
pamsdev: active:0 idle: 20 max:50sa: active:0 idle: 17 max:50
2013-04-16 16:04:43,696 DEBUG super.odbc: active:0 idle: 4 max:50
pamsdev: active:0 idle: 20 max:50
Hello,
The new Tomcat 7 JDBC
poolhttp://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.htmlis
quite new and not much has been written on it yet. Has anyone looked
it
how well it manages underlying resources, both in java domain and in the
database?
More specifically, what happens when I call
On Apr 10, 2013, at 4:05 PM, Igor Urisman wrote:
Hello,
The new Tomcat 7 JDBC
poolhttp://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.htmlis
quite new and not much has been written on it yet.
I'm not sure I would consider it new, it's been out three plus years and I know
it's being
Hi,
Have a look at http://markmail.org/thread/iqgvj34347z77tnc for a bug in
the current Tomcat version and its workaround. This seems to affect
MySQL primarily.
Regards,
Bertrand
On 10/04/2013 4:05 PM, Igor Urisman wrote:
Hello,
The new Tomcat 7 JDBC
poolhttp://people.apache.org/~fhanik
Thanks, Dan et al.
StatementFinalizer is exactly what I was looking for. A quick look at
the source
codehttp://javasourcecode.org/html/open-source/tomcat/tomcat-7.0.29/org/apache/tomcat/jdbc/pool/interceptor/StatementFinalizer.java.html
reveals
exactly what I needed to know: statements
*Hi All,*
Currently we are using tomcat jdbc pooling for oracle 11g R12. The problem
we are facing is during the peak traffic (less than %2) of time the
connections spike up to more than 100 sessions never comes back to the
normal / desired pool size. Due to the connections are returned either
On Apr 8, 2013, at 3:23 AM, Madan KN wrote:
*Hi All,*
Currently we are using tomcat jdbc pooling for oracle 11g R12.
What version of Tomcat are you using? If you are using the pool directly
outside of Tomcat, what version of it are you using?
The problem
we are facing is during the peak
are
not required.*
*
*
*---
*Configuration Being Used*
---
Resource name=jdbc/GlobalHotelsDS auth=Container
type=oracle.jdbc.pool.OracleDataSource
driverClassName
connections during normal operating scenarios evict which are
not required.*
*
*
*---
*Configuration Being Used*
---
Resource name=jdbc/GlobalHotelsDS auth=Container
type
Hi:
But I can see that you aren't using Tomcat JDBC pool, but oracle.jdbc.pool.
OracleDataSource , right ?
And I don't know how you set up your datasource to more than 200 maxActive
connections
Indeed, I don't know how you define the size of connection pool
Regards
2013/4/8 Madan KN madan
-Original Message-
From: Madan KN [mailto:madan...@gmail.com]
Sent: Monday, April 08, 2013 9:29 AM
To: Tomcat Users List
Subject: Re: Tomcat JDBC Pooling - Connections
# 99% percent of the time we do have need for 200 active sessions
across our application cluster. But due to some
Dear All,
JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..
I am getting below error when i m trying to access oracle db using oracle
11g client. It works with earlier oracle client versions. how do i resolve
this. is there any issue with version of ojdbc6.jar that i
Am 2013-04-06 10:30, schrieb dku...@ccilindia.co.in:
Dear All,
JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..
I am getting below error when i m trying to access oracle db using oracle
11g client. It works with earlier oracle client versions. how do i resolve
Hello,
I am using the tomcat jdbc connection pool independently in my web
application which is deployed on glassfish web server. While performing a
database operation, our application goes into a deadlock state. The two
threads involved in the deadlock have the below traces (from a thread
From: amit shah [mailto:amits...@gmail.com]
To: Tomcat Users List; d...@tomcat.apache.org
Do not cross-post. This belongs only on the users list. Read (and follow) the
mailing list usage rules.
Subject: Tomcat JDBC Connection Pool - Deadlock
The two threads involved in the deadlock have
JDBC Connection Pool - Deadlock
The two threads involved in the deadlock have the below traces
(from a thread dump)
You'll need to show the complete traces for both threads, not just the
tail ends.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
From: amit shah [mailto:amits...@gmail.com]
Subject: Re: Tomcat JDBC Connection Pool - Deadlock
I copied the dev group too since it involved technical details (thread
dumps, source code etc). Sorry if that sounds incorrect.
It was incorrect, as is your top-posting. Don't do either
401 - 500 of 1590 matches
Mail list logo
