Re: ConnectionPool JDBC vs. DBCP

Andreas, On 2/16/24 02:21, Döscher, Andreas (ESI) wrote: Moin, in the docpage https://tomcat.apache.org/tomcat-10.1-doc/jdbc-pool.html it says The JDBC Connection Pool org.apache.tomcat.jdbc.pool is a replacement or an alternative to the Apache Commons DBCP connection pool. So why do we

ConnectionPool JDBC vs. DBCP

Moin, in the docpage https://tomcat.apache.org/tomcat-10.1-doc/jdbc-pool.html it says >The JDBC Connection Pool org.apache.tomcat.jdbc.pool is a replacement or an >alternative to the Apache Commons DBCP connection pool. > >So why do we need a new connection pool? > >Here are a

Re: DBCP exception after Tomcat 10.1.13 -> 10.1.14 upgrade

Hi! Thank you for the report. This issue is known and has already been fixed. See https://bz.apache.org/bugzilla/show_bug.cgi?id=67664 Best regards, Konstantin Kolinko вт, 10 окт. 2023 г. в 23:42, Michael Hayes : > > I have just upgraded a working Tomcat 10.1.13 installation to Tomcat 10.1.14,

DBCP exception after Tomcat 10.1.13 -> 10.1.14 upgrade

I have just upgraded a working Tomcat 10.1.13 installation to Tomcat 10.1.14, on Rocky Linux 9.2, PostgreSQL 11.20, JDBC driver 42.6.0, Java 17.0.8. During startup I get this exception: java.sql.SQLException at org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.jav

Re: Handling database connection pooling outside Java, without DBCP et al?

JK, On 11/25/21 04:23, jkla...@iki.fi wrote: On Wednesday, Nov 24, 2021 at 7:37 PM, Christopher Schultz mailto:ch...@christopherschultz.net)> wrote: (on the significance of DBCP overall) It's essentially "failing faster" or, IMO, "failing safer." All right,

Re: Handling database connection pooling outside Java, without DBCP et al?

> On Wednesday, Nov 24, 2021 at 7:37 PM, Christopher Schultz > mailto:ch...@christopherschultz.net)> wrote: > (on the significance of DBCP overall) > It's essentially "failing faster" or, IMO, "failing safer." All right, I think I see it now. A very good

Re: Handling database connection pooling outside Java, without DBCP et al?

ant your application making 1000 simultaneous requests to the proxy. Could you expand on this? Connection pooling is a fundamental aspect of how ProxySQL operates, after all. I'm not familiar with how the DBCP connection pooling works, but what added value would it bring in this case? What does DB

Re: Handling database connection pooling outside Java, without DBCP et al?

n making 1000 simultaneous requests to the proxy. Could you expand on this? Connection pooling is a fundamental aspect of how ProxySQL operates, after all. I'm not familiar with how the DBCP connection pooling works, but what added value would it bring in this case? What does DBCP pooling at the

Re: Handling database connection pooling outside Java, without DBCP et al?

er and for separating read and write traffic to different database instances. After this, we have no need for DBCP or any other Java-level pooling – in fact, having two levels of connection pooling would probably be detrimental to performance, and certainly to our ability to diagnose issues. T

Re: Handling database connection pooling outside Java, without DBCP et al?

recent for your platform. We're in the process of adopting ProxySQL in front of MySQL, to act as the connection pooler and for separating read and write traffic to different database instances. After this, we have no need for DBCP or any other Java-level pooling – in fact, having two levels of con

Re: [OT] Handling database connection pooling outside Java, without DBCP et al?

On 23/11/2021 13:51, Richardson, Diane wrote: I get the emails but how can I send an email for assistance? Please don't hijack threads. See http://tomcat.apache.org/lists.html#taglibs-user Specifically, "Posting questions to the list" Mark ---

Re: [External] Handling database connection pooling outside Java, without DBCP et al?

I get the emails but how can I send an email for assistance? From: jkla...@iki.fi Sent: Tuesday, November 23, 2021 8:23:50 AM To: users@tomcat.apache.org Subject: [External] Handling database connection pooling outside Java, without DBCP et al? This message

Re: Handling database connection pooling outside Java, without DBCP et al?

write traffic to different > database instances. After this, we have no need for DBCP or any other > Java-level pooling – in fact, having two levels of connection pooling would > probably be detrimental to performance, and certainly to our ability to > diagnose issues. The keyword

Handling database connection pooling outside Java, without DBCP et al?

ase instances. After this, we have no need for DBCP or any other Java-level pooling – in fact, having two levels of connection pooling would probably be detrimental to performance, and certainly to our ability to diagnose issues. Trouble is, based on my reading of the JNDI Resources HOW-TO, the Ja

Apache Commons DBCP default configuration for DSpace

Good day I'm wondering what are desirable defaults for a DSpace, open source digital repository software aimed especially at academic, non-profit, and commercial organizations (see https://duraspace.org/dspace/). DSpace supports both Postgres and Oracle and recommends Tomcat, Jetty or Caucho Res

Re: NPE in DBCP when attempting to connect to a database that doesn't exist

eferable, since it gives administrators a better understanding > of what's gone wrong. Seems like a DBCP 1.x bug (not a Tomcat bug) > and I wouldn't consider it a high priority to fix (our product > recovers just fine in either case and we recommend Tomcat 9.0.x > these days), but the disc

NPE in DBCP when attempting to connect to a database that doesn't exist

tuation, Tomcat 7.0.96 throws a NullPointerException with no useful information. I expect an exception, but the 8.5.46/DBCP2 behavior is obviously preferable, since it gives administrators a better understanding of what's gone wrong. Seems like a DBCP 1.x bug (not a Tomcat bug) and I wouldn&

Re: Fix for DBCP-518

>> > >> On Tue, Apr 16, 2019 at 4:28 PM Lazar Kirchev > >> wrote: > >> > >>> Hello, > >>> > >>> Do you have any plans to get the fix for > >>> https://issues.apache.org/jira/browse/DBCP-518 in the Tomcat 8.5 > c

Re: Fix for DBCP-518

will be included in 8.5.41 onwards. Mark > > Mark > > >> >> Regards, >> Lazar >> >> On Tue, Apr 16, 2019 at 4:28 PM Lazar Kirchev >> wrote: >> >>> Hello, >>> >>> Do you have any plans to get the fix for >>

Re: Fix for DBCP-518

gt;> Hello, >> >> Do you have any plans to get the fix for >> https://issues.apache.org/jira/browse/DBCP-518 in the Tomcat 8.5 clone of >> the Commons DBCP? >> The commits with the fix are >> https://github.com/apache/commons-dbcp/commit/81aea944160608838cb2d

Re: Fix for DBCP-518

Hello, Any update on this? Regards, Lazar On Tue, Apr 16, 2019 at 4:28 PM Lazar Kirchev wrote: > Hello, > > Do you have any plans to get the fix for > https://issues.apache.org/jira/browse/DBCP-518 in the Tomcat 8.5 clone of > the Commons DBCP? > The commits with t

Fix for DBCP-518

Hello, Do you have any plans to get the fix for https://issues.apache.org/jira/browse/DBCP-518 in the Tomcat 8.5 clone of the Commons DBCP? The commits with the fix are https://github.com/apache/commons-dbcp/commit/81aea944160608838cb2d7cdfb0d9b6893a655d9, https://github.com/apache/commons-dbcp

tomcat-dbcp Poolable connection is closed while connection is in ALLOCATED state

Hi, In the java application (using tomcat 7, JDK 7u51, tomcat-dbcp-8.0.3.jar, ojdbc6.jar) there is a certain connection leak. After the connection pool was exhausted (pool reached maxTotal active connections), I took heap dump. On analyzing heap dump, as expected maxTotal PoolableConnection and

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

pool configuration and when the connection is grabbed from the pool. I've since changed the code to not touch the autocommit setting and leave that up to the datasource (resource config in context.xml) >>> On 10/13/17 10:17 AM, Chris Cheshire wrote: >>>> >>>

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

quot;. In other >> words, you do not use (tomcat)DBCP, you are using Tomcat >> jdbc-pool. > > That's what I meant sorry. Was comparing to commons-dbcp and went > dyslexic on the acronyms. > >> >> In DBCP, the default of rollbackOnReturn attribute i

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

e.g. a connection-pool then you'll have to make sure that you configure them to be NOT auto-commit. This is not a setting that you can control from the server. More below. >> On 10/13/17 10:17 AM, Chris Cheshire wrote: >>> >>> >>> As a further test I just took

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

On Tue, Oct 17, 2017 at 3:44 AM, Keiichi Fujino wrote: > Hi > > You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory". > In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool. That's what I meant sorry. Was comparing to commons-db

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

Hi You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory". In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool. In DBCP, the default of rollbackOnReturn attribute is true. However, in Tomcat jdbc-pool, the default of rollbackOnReturn( and comm

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

y >> DAOFactory close() method, and swapped back to commons dbcp. Added >> an update that wasn't explicitly committed, and it correctly did >> not get committed when the connection was closed. Swapped back to >> tomcat dbcp and repeated, it got committed without an expl

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

I just took out my explicit rollback in my > DAOFactory close() method, and swapped back to commons dbcp. Added > an update that wasn't explicitly committed, and it correctly did > not get committed when the connection was closed. Swapped back to > tomcat dbcp and repeated, it got co

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

As a further test I just took out my explicit rollback in my DAOFactory close() method, and swapped back to commons dbcp. Added an update that wasn't explicitly committed, and it correctly did not get committed when the connection was closed. Swapped back to tomcat dbcp and repeated, i

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

On Thu, Oct 12, 2017 at 11:16 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Chris, > > On 10/11/17 5:21 PM, Chris Cheshire wrote: >> Working on a migration from 7 to 8.5, and in it I am now using the >> tomcat dbcp, instead o

Re: tomcat 8.5.23 dbcp not honoring autocommit = false?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 10/11/17 5:21 PM, Chris Cheshire wrote: > Working on a migration from 7 to 8.5, and in it I am now using the > tomcat dbcp, instead of apache commons dbcp.> I have found that > with no other changes to the db code (except

tomcat 8.5.23 dbcp not honoring autocommit = false?

Working on a migration from 7 to 8.5, and in it I am now using the tomcat dbcp, instead of apache commons dbcp. I have found that with no other changes to the db code (except the factory param for the resource), it is working fine other than there is an implicit commit happening when I close a

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bradley, On 10/7/15 4:04 PM, Bradley Wagner wrote: >> The general recommendation is to use the default pool >> (commons-dbcp). > > Great. Thanks! > >> Unless you have narrowed a performance problem to the pool >&g

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

> The general recommendation is to use the default pool (commons-dbcp). Great. Thanks! > Unless you have narrowed a performance problem to the pool itself, there's no reason to use one over the other. I suspect that there are only a few companies in the world where the conn

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

ly confusing to those you don't already understand. "DBCP" usually just means "database connection pool", but in the Apache world, it usually specifically means commons-dbcp. > Is it your recommendation then to use DBCP 2 over Tomcat JDBC in > Tomcat 8? If so, I think i

Re: DBCP params different for the Tomcat JDBC (not DBCP) implementation in Tomcat 8?

Ah, I see what you're saying. My apologies for not seeing that sooner. That post was also very helpful in explaining why both exist. Thank you! Is it your recommendation then to use DBCP 2 over Tomcat JDBC in Tomcat 8? If so, I think it would be helpful to have a page on the public T

Re: DBCP params different for the Tomcat DBCP implementation in Tomcat 8?

On 07/10/2015 19:54, Bradley Wagner wrote: > Did not what? > > We added "factory='org.apache.tomcat.jdbc.pool.DataSourceFactory'". That > switched us to Tomcat DBCP, correct? No. There is no such thing as Tomcat DBCP. There is Apache Commons DBCP 1. This is use

Re: DBCP params different for the Tomcat DBCP implementation in Tomcat 8?

Did not what? We added "factory='org.apache.tomcat.jdbc.pool.DataSourceFactory'". That switched us to Tomcat DBCP, correct? At that time, we were using the updated "maxWaitMillis" and "maxTotal" in our context.xml and Tomcat didn't seem to com

Re: DBCP params different for the Tomcat DBCP implementation in Tomcat 8?

2015-10-07 21:36 GMT+03:00 Bradley Wagner : > Hi, > > We recently upgraded to Tomcat 8. As per the Migration Guide: > https://tomcat.apache.org/migration-8.html#Database_Connection_Pooling and > DBCP documentation > https://tomcat.apache.org/tomcat-8.0-doc/jndi-datasource-e

DBCP params different for the Tomcat DBCP implementation in Tomcat 8?

Hi, We recently upgraded to Tomcat 8. As per the Migration Guide: https://tomcat.apache.org/migration-8.html#Database_Connection_Pooling and DBCP documentation https://tomcat.apache.org/tomcat-8.0-doc/jndi-datasource-examples-howto.html#Database_Connection_Pool_(DBCP_2)_Configurations, we

Re: validationQuery doesn't work (DBCP 7.0.59)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jose, On 6/23/15 6:46 AM, Jose María Zaragoza wrote: > 2015-06-15 17:59 GMT+02:00 Christopher Schultz > : Jose, > > It looks like your issue is mostly solved... > > On 6/15/15 4:42 AM, Jose María Zaragoza wrote: I'm using Tomcat 7.0.59 and Po

Re: validationQuery doesn't work (DBCP 7.0.59)

2015-06-15 17:59 GMT+02:00 Christopher Schultz : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Jose, > > It looks like your issue is mostly solved... > > On 6/15/15 4:42 AM, Jose María Zaragoza wrote: >> I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 >> >> The context.x

Re: validationQuery doesn't work (DBCP 7.0.59)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jose, It looks like your issue is mostly solved... On 6/15/15 4:42 AM, Jose María Zaragoza wrote: > I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 > > The context.xml settings are > > > timeBetweenEvictionRunsMillis="0"/> Ar

Re: validationQuery doesn't work (DBCP 7.0.59)

2015-06-15 16:35 GMT+02:00 Daniel Mikusa : > On Mon, Jun 15, 2015 at 4:42 AM, Jose María Zaragoza > wrote: > >> Hello: >> >> >> I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 >> >> The context.xml settings are >> >> >> > factory="org.apache.tomcat.jdbc.pool.Dat

Re: validationQuery doesn't work (DBCP 7.0.59)

uerying database. Cause: >> org.postgresql.util.PSQLException: This connection has been closed. >> >> How is it possible if testOnBorrow="true" and validationQuery="SELECT 1" ? >> > > Try setting validationInterval to a lower value. It defaults to

Re: validationQuery doesn't work (DBCP 7.0.59)

On Mon, Jun 15, 2015 at 4:42 AM, Jose María Zaragoza wrote: > Hello: > > > I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 > > The context.xml settings are > > >factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" driverClassName="org.po

Re: validationQuery doesn't work (DBCP 7.0.59)

t;>>> When I test this configuration ( I stop/start databases but , at >>>> least, there is one running ) , sometimes I'm getting this error >>>> message: >>>> >>>> >>>> org.apache.ibatis.exceptions.PersistenceException: >

Re: validationQuery doesn't work (DBCP 7.0.59)

On 15/06/2015 11:39, Jose María Zaragoza wrote: > 2015-06-15 11:39 GMT+02:00 Mark Thomas : >> On 15/06/2015 09:42, Jose María Zaragoza wrote: >>> Hello: >>> >>> >>> I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 >>> >>> The context.xml settings are >>> >>> >>> >>

Re: validationQuery doesn't work (DBCP 7.0.59)

2015-06-15 11:39 GMT+02:00 Mark Thomas : > On 15/06/2015 09:42, Jose María Zaragoza wrote: >> Hello: >> >> >> I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 >> >> The context.xml settings are >> >> >> > factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" >>

Re: validationQuery doesn't work (DBCP 7.0.59)

On 15/06/2015 09:42, Jose María Zaragoza wrote: > Hello: > > > I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 > > The context.xml settings are > > >factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" > driverClassName="org.postgresql

Re: validationQuery doesn't work (DBCP 7.0.59)

You can change the DB log parameter "log_statement" setting to ALL for the time being and ensure the query execution. On Mon, Jun 15, 2015 at 2:12 PM, Jose María Zaragoza wrote: > Hello: > > > I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 > > The context.xml settings are >

validationQuery doesn't work (DBCP 7.0.59)

Hello: I'm using Tomcat 7.0.59 and PostgreSQL JDBC driver 9.4-1201-jdbc4 The context.xml settings are I've configured JDBC driver in failover mode ( as you can see in URL definition ) When I test this configuration ( I stop/start databases but , at least, there is one running ) , sometimes

Re: Tomcat DBCP 8.0.18 issue

Hmm, interesting... Thanks for explanation Mark! 2015-06-03 12:22 GMT+03:00 Mark Thomas : > On 03/06/2015 07:24, Tweak Ronaldo wrote: > > Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. > > Although I don't understand why Tomcat JDBC don&#

Re: Tomcat DBCP 8.0.18 issue

mixed together Tomcat JDBC 8 and DBCP 7, my bad. > > Although I don't understand why Tomcat JDBC don't use DBCP as default > > solution for connections pooling. > > Tomcat does - and always has - used Commons DBCP for connection pooling > by default. > > We do pac

Re: Tomcat DBCP 8.0.18 issue

On 03/06/2015 07:24, Tweak Ronaldo wrote: > Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. > Although I don't understand why Tomcat JDBC don't use DBCP as default > solution for connections pooling. Tomcat does - and always has - used Commons DBCP for

Re: Tomcat DBCP 8.0.18 issue

Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. Although I don't understand why Tomcat JDBC don't use DBCP as default solution for connections pooling. 2015-06-02 16:59 GMT+03:00 Mark Thomas : > On 01/06/2015 14:22, Tweak Ronaldo wrote: > > Hello guy

Re: Tomcat DBCP 8.0.18 issue

2015-06-01 16:22 GMT+03:00 Tweak Ronaldo : > Hello guys, we have migrated to Tomcat DBCP 8.0.18 from 7.0.37 recently and > faced the following issue: > after database restart (Postgres), our application wasn't been able to > restore connectivity to DB, all connections were clos

Re: Tomcat DBCP 8.0.18 issue

On 01/06/2015 14:22, Tweak Ronaldo wrote: > Hello guys, Assuming you don't want to limit your question to men only, you would be better to use of of the following greetings: Hello, Hello all, Hello folks, etc. > we have migrated to Tomcat DBCP 8.0.18 from 7.0.37 recently and

Tomcat DBCP 8.0.18 issue

Hello guys, we have migrated to Tomcat DBCP 8.0.18 from 7.0.37 recently and faced the following issue: after database restart (Postgres), our application wasn't been able to restore connectivity to DB, all connections were closed and every time, after failed attempt to execute some SQL stat

Re: tomcat-jdbc vs. tomcat-dbcp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Christian, On 11/28/14 7:57 AM, Christian wrote: > reading tomcat 8.x documentation, I don't find anything about > tomcat-dbcp. The use of tomcat-jdbc is described at [1]. Some of > the disadvantages just apply for DBCP 1.x.

tomcat-jdbc vs. tomcat-dbcp

Hi, reading tomcat 8.x documentation, I don't find anything about tomcat-dbcp. The use of tomcat-jdbc is described at [1]. Some of the disadvantages just apply for DBCP 1.x. Is the use of tomcat-jdbc still recommended compared to the repackaged DBCP 2.x in tomcat-dbcp package? Re

Re: Error in DBCP Connection Pool with tomcat 6.x

On Thu, Jul 3, 2014 at 9:11 PM, Propes, Barry L wrote: > Good to hear. > > -Original Message- > From: Vijendra Pachoriya [mailto:vijendra.pachor...@indegene.com] > Sent: Thursday, July 03, 2014 8:22 AM > To: Tomcat Users List > Subject: RE: Error in DBCP Connection

RE: Error in DBCP Connection Pool with tomcat 6.x

Good to hear. -Original Message- From: Vijendra Pachoriya [mailto:vijendra.pachor...@indegene.com] Sent: Thursday, July 03, 2014 8:22 AM To: Tomcat Users List Subject: RE: Error in DBCP Connection Pool with tomcat 6.x Thanks everyone !! Managed to solve the issue. It seems the wait

RE: Error in DBCP Connection Pool with tomcat 6.x

: 02 July 2014 22:33 To: Tomcat Users List Subject: Re: Error in DBCP Connection Pool with tomcat 6.x On 7/1/14, 10:48 PM, Vijendra Pachoriya wrote: > Hi Filip, > > This error comes at some point of time on production, when the server is on > load. > > I am using hibernate a

Re: Error in DBCP Connection Pool with tomcat 6.x

On 7/1/14, 10:48 PM, Vijendra Pachoriya wrote: > Hi Filip, > > This error comes at some point of time on production, when the server is on > load. > > I am using hibernate and not closing any connection manually, its all managed > by hibernate and tomcat dbcp connection

Re: Error in DBCP Connection Pool with tomcat 6.x

t; managed by hibernate and tomcat dbcp connection pool. > > For me it seems like DBCP is trying to close the connection which is > already closed by the database server. > Have you tried looking at your database server logs to see if it's closing the connection? You mentioned it&

RE: Error in DBCP Connection Pool with tomcat 6.x

Hi Filip, This error comes at some point of time on production, when the server is on load. I am using hibernate and not closing any connection manually, its all managed by hibernate and tomcat dbcp connection pool. For me it seems like DBCP is trying to close the connection which is already

Re: Error in DBCP Connection Pool with tomcat 6.x

; Sent: Tuesday, July 01, 2014 2:31 AM > To: users@tomcat.apache.org > Cc: Alok Roy > Subject: Error in DBCP Connection Pool with tomcat 6.x > > Hi Tomcat Team, > > Please help me out in solving below error. > > Below is the details : > >

RE: Error in DBCP Connection Pool with tomcat 6.x

-Original Message- From: Vijendra Pachoriya [mailto:vijendra.pachor...@indegene.com] Sent: Tuesday, July 01, 2014 2:31 AM To: users@tomcat.apache.org Cc: Alok Roy Subject: Error in DBCP Connection Pool with tomcat 6.x Hi Tomcat Team, Please help me out in solving below error. Below

Error in DBCP Connection Pool with tomcat 6.x

Hi Tomcat Team, Please help me out in solving below error. Below is the details : Configuration in my context.xml ==Error Message at org.apache.jk.common.ChannelSocket.processC

Re: Create XA Datasource with DBCP/Tomcat 6

On 22/01/2014 17:04, Sylvain Goulmy wrote: > Hi, > > I'd like to create a XA datasource within Tomcat 6 but i don't find any > example to do so. Tomcat6 provides its own dbcp package but when i compare > it to the standard dbcp package i notice that class related to XA

Create XA Datasource with DBCP/Tomcat 6

Hi, I'd like to create a XA datasource within Tomcat 6 but i don't find any example to do so. Tomcat6 provides its own dbcp package but when i compare it to the standard dbcp package i notice that class related to XA Driver are missing. The following classes : org/apache/commons/db

Re: DBCP : Best practice javax.sql.DataSource object and Connection Object creation in Web Application

my practice. > > - Using DBCP, I created javax.sql.DataSource and > connection object for each call to method in my class. > > - Right now I am facing oracle session blocking problem. > > > > B) I am going to implement following practice >

DBCP : Best practice javax.sql.DataSource object and Connection Object creation in Web Application

Dear All, I would like to know that what is the best practice or efficient way to create javax.sql.DataSource object A) Following is my practice. - Using DBCP, I created javax.sql.DataSource and connection object for each call to method in my class. - Right now I

Re: [OT] Curious difference in connection behaviour on database side DBCP vs. JDBC?

On 22.11.2013, at 02:20, Christopher Schultz 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

Re: [OT] Curious difference in connection behaviour on database side DBCP vs. JDBC?

lso states that one can get away with not doing so). > > 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 file a docu

Re: [OT] Curious difference in connection behaviour on database side DBCP vs. JDBC?

says it is best practice to explicitly close the JDBC resources as early as possible, but it also states that one can get away with not doing so). 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

Re: [OT] Curious difference in connection behaviour on database side DBCP vs. JDBC?

the >>> application, (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? >> >> Com

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

"600" maxWait="1"/> > > > The behaviour applies to ALL queries/statements from the > application. > > I have here an example of the way we close from the application, > (the devs have named it dispose). From my untrained non java dev > eye we do not seem to

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

ose(); 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 the associated Statements and ResultSets when the connection that > created them is ret

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

On Nov 19, 2013, at 8:32 AM, Carl Boberg wrote: > 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.

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

On 19/11/2013 13:32, Carl Boberg wrote: > I have here an example of the way we close from the application, (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, w

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

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 these are

Re: Curious difference in connection behaviour on database side DBCP vs. JDBC?

On Nov 18, 2013, at 9:48 AM, Carl Boberg 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

Curious difference in connection behaviour on database side DBCP vs. JDBC?

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...

Re: DBCP is Single Threaded

rrency levels you need > to reach to hit this bottleneck - if you use a recent version of > Pool and DBCP. Agreed. Presumably, a Connection is being checked-out of the pool in order to ... make some JDBC calls. Those are going to be way slower than any of this synchronization we're di

Re: DBCP is Single Threaded

have a hard time believing most real world apps would actually get anywhere near the concurrency levels you need to reach to hit this bottleneck - if you use a recent version of Pool and DBCP. If you use the versions of 4 years ago then hitting the bottleneck is easy. You can use the unit test

Re: DBCP is Single Threaded

>>> connection pool is a major improvement. I read that >> >>> commons-dbcp is single threaded, in order to be thread safe >>> commons-dbcp locks the entire pool, even during query >>> validation. >> >>> So as i understand, the connection

Re: DBCP is Single Threaded

On 07/11/2013 16:08, Christopher Schultz wrote: > Mark, > > On 11/7/13, 11:03 AM, Mark Thomas wrote: >> On 07/11/2013 15:58, yogesh hingmire wrote: >>> While looking to upgrade to tomcat7, i understand the >>> connection pool is a major improvement. I read tha

Re: DBCP is Single Threaded

On 07/11/2013 16:03, Christopher Schultz wrote: > Yogesh, > > On 11/7/13, 10:58 AM, yogesh hingmire wrote: >> While looking to upgrade to tomcat7, i understand the connection >> pool is a major improvement. I read that > >> commons-dbcp is single threaded, in order

Re: DBCP is Single Threaded

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 11/7/13, 11:03 AM, Mark Thomas wrote: > On 07/11/2013 15:58, yogesh hingmire wrote: >> While looking to upgrade to tomcat7, i understand the connection >> pool is a major improvement. I read that >> >> commons-

Re: DBCP is Single Threaded

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Yogesh, On 11/7/13, 10:58 AM, yogesh hingmire wrote: > While looking to upgrade to tomcat7, i understand the connection > pool is a major improvement. I read that > > commons-dbcp is single threaded, in order to be thread safe > com

Re: DBCP is Single Threaded

On 07/11/2013 15:58, yogesh hingmire wrote: > While looking to upgrade to tomcat7, i understand the connection pool is a > major improvement. I read that > > commons-dbcp is single threaded, in order to be thread safe commons-dbcp > locks the entire pool, even during query validat

DBCP is Single Threaded

While looking to upgrade to tomcat7, i understand the connection pool is a major improvement. I read that commons-dbcp is single threaded, in order to be thread safe commons-dbcp locks the entire pool, even during query validation. So as i understand, the connection pool will be locked when

Re: Tomcat DBCP Logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rahul, On 3/6/13 12:49 PM, Rahul Somasunderam wrote: > I'm running Tomcat 7.0.23. I've got a question about configuring > the logging of DBCP Failures. Echoing Daniel's suggestion: upgrade. > I've go this in my conte

Re: Tomcat DBCP Logging

o do much with tomcat being old. I think >> it's with me having to configure the logging correctly. > > You're right, this is not related to the issue at hand. It's just a general > reminder :) > >> >>> >>>> I've got a question a

Re: Tomcat DBCP Logging

getting pretty old, you might want to consider upgrading. > > I will, but I don't think this has to do much with tomcat being old. I think > it's with me having to configure the logging correctly. You're right, this is not related to the issue at hand. It's jus

Re: Tomcat DBCP Logging

has to do much with tomcat being old. I think it's with me having to configure the logging correctly. > >> I've got a question about configuring the logging of DBCP Failures. >> >> I've go this in my context xml file. >> >> >>

  1   2   3   4   5   6   >