Re: [c3p0-users] debugUnreturnedConnectionStackTraces, unreturnedConnectionTimeout doesn't seem work; maxIdleTimeExcessConnections rarely works

[aspdeepak_am <asp...@gm...>]

I have identified the problem with my 1st issue. It doesnot seem to be an
issue since by default c3po uses 'initialPoolSize -> 3'.

And 4th (debugUnreturnedConnectionStackTraces) is not an issue at all since
there is no connection leak, so no INFO level stack traces.
But I am still unclear about the 2nd issue.


aspdeepak_am wrote:
> 
> In my application I have several data-sources opened at a same time.
> 
> And each of the datasource has its own pool.
> 
> I had several issues in my early stages of development, I will summarize
> them below.
> 
> 1. Even though i have configured acquireIncrement to 1, I found that there
> were several increments for the very first time the datasource is loaded.
> 2. Even though the connections are properly returned(closed by clients) to
> the pool, they remain idle and unused and new connections are created
> instead of reusing the existing idle connections. I confirmed this by
> tracing 'NumBusyConnectionsAllUsers' and 'NumIdleConnectionsAllUsers'. 
> 3. Then I tried to kill all the idle connections by setting
> 'maxIdleTimeExcessConnections' to 300 seconds. Unfortunately this was also
> unpredictable, since if the delay increases they were not closed exactly
> after 300 sec (but they some how got killed eventually, but definitely a
> much longer time than specified 300 seconds).
> 4. I tried of debugging them all by setting unreturnedConnectionTimeout
> and debugUnreturnedConnectionStackTraces but no gain here as well. But
> before doing this step I disabled maxIdleTimeExcessConnections option. I
> think unreturnedConnectionTimeout doesnot work because all the connections
> are properly returned to the pool, So I guess my 2nd point holds good.
> 
> Please have a look at the ComboPooledDataSource created as per my 4th
> stage.
> 
> 2011-07-04 14:52:58,094 INFO  [ConnectionManager] pooled datasource for
> jbossportal: com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement
> -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000,
> autoCommitOnClose -> false, automaticTestTable -> null,
> breakAfterAcquireFailure -> false, checkoutTimeout -> 0,
> connectionCustomizerClassName -> null, connectionTesterClassName ->
> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName ->
> z8kfsx8g1vz6f3vzz93nt|46f87198, debugUnreturnedConnectionStackTraces ->
> true, description -> null, driverClass -> com.mysql.jdbc.Driver,
> factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false,
> identityToken -> z8kfsx8g1vz6f3vzz93nt|46f87198, idleConnectionTestPeriod
> -> 0, initialPoolSize -> 3, jdbcUrl ->
> jdbc:mysql://localhost:3306/jbossportal?autoReconnect=true&serverTimezone=UTC,
> maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0,
> maxIdleTimeExcessConnections -> 0, maxPoolSize -> 10, maxStatements -> 0,
> maxStatementsPerConnection -> 0, minPoolSize -> 0, numHelperThreads -> 3,
> numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> null,
> properties -> {user=******, password=******}, propertyCycle -> 0,
> testConnectionOnCheckin -> false, testConnectionOnCheckout -> false,
> unreturnedConnectionTimeout -> 100, usesTraditionalReflectiveProxies ->
> false ]
> 
> Any help on this is greatly appreciable.
> 

-- 
View this message in context: http://old.nabble.com/debugUnreturnedConnectionStackTraces%2C-unreturnedConnectionTimeout-doesn%27t-seem-work---maxIdleTimeExcessConnections--rarely-works-tp31989211p31994937.html
Sent from the c3p0 - users mailing list archive at Nabble.com.