[jira] Commented: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514497 ] Phil Steitz commented on POOL-97: - A more conservative solution would be to revert to the pool 1.2 setup where the

[jira] Resolved: (DBCP-11) [dbcp] stmt.getConnection() != Connection used to create the statement

[ https://issues.apache.org/jira/browse/DBCP-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-11. - Resolution: Fixed Patch applied. Thanks. [dbcp] stmt.getConnection() != Connection used to create the

[jira] Resolved: (POOL-94) GenericObjectPool allows checking in of previously checked in objects

[ https://issues.apache.org/jira/browse/POOL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved POOL-94. - Resolution: Won't Fix Javadoc has been updated to include a warning. GenericObjectPool allows checking

[jira] Resolved: (DBCP-232) maxWait = 0 waits indefinitely too, not only maxWait = -1

[ https://issues.apache.org/jira/browse/DBCP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-232. -- Resolution: Fixed Javadoc fix committed in r558394. Thanks for reporting thi maxWait = 0 waits

[jira] Commented: (MATH-167) ConvergenceException in normal CDF

[ https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514453 ] Phil Steitz commented on MATH-167: -- Fixed for nomal distribution in r558450. Leaving open because we should look at

[jira] Updated: (MATH-167) ConvergenceException in normal CDF

[ https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-167: - Fix Version/s: 1.2 ConvergenceException in normal CDF --

[jira] Resolved: (DBCP-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?

[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-209. -- Resolution: Invalid I agree with Dain. For BasicDataSource, the username and password are pool

[jira] Resolved: (DBCP-233) Allow connection, statement, and result set to be closed multiple times

[ https://issues.apache.org/jira/browse/DBCP-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-233. -- Resolution: Fixed Patch applied. Many thanks. Allow connection, statement, and result set to be

[jira] Resolved: (DBCP-134) [dbcp] DelegatingConnection.close() throws exception

[ https://issues.apache.org/jira/browse/DBCP-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-134. -- Resolution: Fixed Fixed in r 557176. [dbcp] DelegatingConnection.close() throws exception

[jira] Resolved: (DBCP-3) [dbcp] PoolableConnection.close() won't allow multiple close

[ https://issues.apache.org/jira/browse/DBCP-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-3. Resolution: Fixed Fixed in r 557176. [dbcp] PoolableConnection.close() won't allow multiple close

[jira] Resolved: (DBCP-5) [dbcp] PoolGuardConnectionWrapper violates close() contract

[ https://issues.apache.org/jira/browse/DBCP-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-5. Resolution: Fixed Fixed in r 557176. [dbcp] PoolGuardConnectionWrapper violates close() contract

[jira] Resolved: (DBCP-23) [dbcp] SQLException When PoolablePreparedStatement Already Closed

[ https://issues.apache.org/jira/browse/DBCP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-23. - Resolution: Fixed Fixed in r 557176. [dbcp] SQLException When PoolablePreparedStatement Already Closed

[jira] Resolved: (DBCP-230) [DBCP] BasicManagedDataSource

[ https://issues.apache.org/jira/browse/DBCP-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-230. -- Resolution: Fixed Patch applied. Thanks! [DBCP] BasicManagedDataSource -

[jira] Reopened: (MATH-160) Chi-Square Test for Comparing two binned Data Sets

[ https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz reopened MATH-160: -- Good catch, Luc. I thought clirr was set up to fail the build when this happens. In any case, this needs

[jira] Commented: (MATH-167) ConvergenceException in normal CDF

[ https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510905 ] Phil Steitz commented on MATH-167: -- Thanks for reporting this. I see three alternatives to address - appreciate

[jira] Resolved: (DBCP-228) [dbcp] Managed Connection support

[ https://issues.apache.org/jira/browse/DBCP-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-228. -- Resolution: Fixed Patch applied. Thanks! [dbcp] Managed Connection support

[jira] Resolved: (MATH-160) Chi-Square Test for Comparing two binned Data Sets

[ https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-160. -- Resolution: Fixed Applied a modified version of the patch, along with test cases, verified against

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Attachment: timer.patch EVICTION_TIMER is never cancelled. --

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Attachment: timer.patch Attaching a patch (timer.patch) that makes the eviction timer a (lazy initialized)

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Attachment: (was: timer.patch) EVICTION_TIMER is never cancelled. --

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Attachment: (was: timer.patch) EVICTION_TIMER is never cancelled. --

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Attachment: timer.patch EVICTION_TIMER is never cancelled. --

[jira] Updated: (POOL-102) Thread waiting forever for borrowObject() cannot be interrupted

[ https://issues.apache.org/jira/browse/POOL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-102: - Fix Version/s: 2.0 Affects Version/s: 1.1 1.2 Thread waiting forever for

[jira] Resolved: (POOL-102) Thread waiting forever for borrowObject() cannot be interrupted

[ https://issues.apache.org/jira/browse/POOL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved POOL-102. -- Resolution: Fixed Patch applied. Thanks! Thread waiting forever for borrowObject() cannot be

[jira] Updated: (POOL-97) EVICTION_TIMER is never cancelled.

[ https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated POOL-97: Fix Version/s: 2.0 EVICTION_TIMER is never cancelled. --

[jira] Resolved: (POOL-95) GenericObjectPool constructor with GenericObjectPool.Config ignores softMinEvictableIdleTimeMillis

[ https://issues.apache.org/jira/browse/POOL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved POOL-95. - Resolution: Fixed Fix Version/s: 2.0 Fix has been applied and will be included in 2.0

[jira] Commented: (POOL-98) Make GenericObjectPool better extensible

[ https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506784 ] Phil Steitz commented on POOL-98: - OK, I understand the use case, but with the 1.3 pool impl, I don't think what you

[jira] Reopened: (POOL-86) GenericKeyedObjectPool retaining too many idle objects

[ https://issues.apache.org/jira/browse/POOL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz reopened POOL-86: - Assignee: Phil Steitz (was: Sandy McArthur) I agree with Rob that a better solution should be provided -

[jira] Commented: (DBCP-216) Improvement of error recovery in KeyedCPDSConnectionFactory

[ https://issues.apache.org/jira/browse/DBCP-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506620 ] Phil Steitz commented on DBCP-216: -- Patch looks correct and appropriate to me, subject to the comments below.

[jira] Updated: (DBCP-97) setAutoCommit(true) when returning connection to the pool

[ https://issues.apache.org/jira/browse/DBCP-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-97: Fix Version/s: 1.3 setAutoCommit(true) when returning connection to the pool

[jira] Updated: (DBCP-225) getConnection / borrowObject fails with NullPointerException

[ https://issues.apache.org/jira/browse/DBCP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-225: - Fix Version/s: 1.3 getConnection / borrowObject fails with NullPointerException

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506646 ] Phil Steitz commented on DBCP-212: -- PoolableConnectionFactory.makeObject() has been synchronized since the initial

[jira] Commented: (POOL-98) Make GenericObjectPool better extensible

[ https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506659 ] Phil Steitz commented on POOL-98: - I don't think we want to expose the _pool, since this is actually a linked list of

[jira] Resolved: (MATH-166) Special functions not very accurate

[ https://issues.apache.org/jira/browse/MATH-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-166. -- Resolution: Fixed Patch applied. Thanks Special functions not very accurate

[jira] Resolved: (MATH-158) Arbitrary log

[ https://issues.apache.org/jira/browse/MATH-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-158. -- Resolution: Fixed Modified version of patch applied. Changes: made arguments doubles and used

[jira] Reopened: (DBCP-102) [dbcp] setReadOnly setAutoCommit called too many times

[ https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz reopened DBCP-102: -- [dbcp] setReadOnly setAutoCommit called too many times

[jira] Updated: (DBCP-102) [dbcp] setReadOnly setAutoCommit called too many times

[ https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-102: - Fix Version/s: (was: 1.2.2) 1.3 Setting fix level to 1.3, as fix represents a

[jira] Reopened: (DBCP-97) setAutoCommit(true) when returning connection to the pool

[ https://issues.apache.org/jira/browse/DBCP-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz reopened DBCP-97: - Need to verify this fix is correct and necessary. setAutoCommit(true) when returning connection to the pool

[jira] Created: (DBCP-226) DBCP should support configuration of queryTimeout for validation queries

DBCP should support configuration of queryTimeout for validation queries Key: DBCP-226 URL: https://issues.apache.org/jira/browse/DBCP-226 Project: Commons Dbcp Issue

[jira] Resolved: (MATH-163) The evaluate method and the getResult method of class Variance give different results

[ https://issues.apache.org/jira/browse/MATH-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-163. -- Resolution: Won't Fix Javadoc clarification has been made. The evaluate method and the getResult

[jira] Commented: (MATH-160) Chi-Square Test for Comparing two binned Data Sets

[ https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503276 ] Phil Steitz commented on MATH-160: -- With the reference in the last comment replacing the reference in the patch,

[jira] Resolved: (MATH-82) [math] FractionFormatTest doesn't compile under JDK 1.3

[ https://issues.apache.org/jira/browse/MATH-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-82. - Resolution: Won't Fix Nothing we can do about incorrect JDK behavior. [math] FractionFormatTest doesn't

[jira] Updated: (MATH-166) Special functions not very accurate

[ https://issues.apache.org/jira/browse/MATH-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-166: - Fix Version/s: 1.2 I see no reason not to apply this patch for 1.2. Special functions not very accurate

[jira] Updated: (MATH-158) Arbitrary log

[ https://issues.apache.org/jira/browse/MATH-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-158: - Fix Version/s: 1.2 Arbitrary log - Key: MATH-158 URL:

[jira] Updated: (MATH-160) Chi-Square Test for Comparing two binned Data Sets

[ https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-160: - Fix Version/s: 1.2 Chi-Square Test for Comparing two binned Data Sets

[jira] Updated: (MATH-154) MathUtils addAndCheck and subAndCheck for long values

[ https://issues.apache.org/jira/browse/MATH-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-154: - Fix Version/s: 1.2 MathUtils addAndCheck and subAndCheck for long values

[jira] Updated: (MATH-163) The evaluate method and the getResult method of class Variance give different results

[ https://issues.apache.org/jira/browse/MATH-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated MATH-163: - Fix Version/s: 1.2 The evaluate method and the getResult method of class Variance give different

[jira] Commented: (DBCP-225) getConnection / borrowObject fails with NullPointerException

[ https://issues.apache.org/jira/browse/DBCP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499420 ] Phil Steitz commented on DBCP-225: -- Based on the stack traces, it looks like you are using pool 1.2, correct? From

[jira] Commented: (DBCP-224) Null delegate possible

[ https://issues.apache.org/jira/browse/DBCP-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499421 ] Phil Steitz commented on DBCP-224: -- Stack traces are from dbcp 1.2.1, pool 1.2 Null delegate possible

[jira] Updated: (DBCP-218) basicDataSource.setLoginTimeout(n) not work?

[ https://issues.apache.org/jira/browse/DBCP-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-218: - Affects Version/s: 1.1 1.2 1.2.1 Fix Version/s: 1.3

[jira] Updated: (DBCP-223) Auto-alert of connection pool critical events?

[ https://issues.apache.org/jira/browse/DBCP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-223: - There are no current or planned features for this kind of thing, though improved logging has been discussed.

[jira] Updated: (DBCP-221) How to close the connection pool without shutting down the JVM while there are connections being used?

[ https://issues.apache.org/jira/browse/DBCP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-221: - Fix Version/s: 1.3 Behavior here is determined by the underlying pool. In the case of commons pool's

[jira] Resolved: (DBCP-222) Does DBCP closes unclosed PreparedStatement or resultset?

[ https://issues.apache.org/jira/browse/DBCP-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-222. -- Resolution: Invalid Questions such as this should be directed to the commons-user mailing list. I am

[jira] Resolved: (DBCP-220) Is there any UI developed for the connection pool?

[ https://issues.apache.org/jira/browse/DBCP-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-220. -- Resolution: Won't Fix A management UI is out of scope for commons dbcp or pool. We want to keep these

[jira] Commented: (MATH-164) Complex - Issue with non-compliance to C99!

[ https://issues.apache.org/jira/browse/MATH-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494617 ] Phil Steitz commented on MATH-164: -- I agree with Richard here and will add a little historical context. Initially,

[jira] Commented: (POOL-94) GenericObjectPool allows checking in of previously checked in objects

[ https://issues.apache.org/jira/browse/POOL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490673 ] Phil Steitz commented on POOL-94: - Another bad thing that can happen if an object instance is returned to the pool

[jira] Commented: (POOL-95) GenericObjectPool constructor with GenericObjectPool.Config ignores softMinEvictableIdleTimeMillis

[ https://issues.apache.org/jira/browse/POOL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489006 ] Phil Steitz commented on POOL-95: - Any reason not to apply this patch? GenericObjectPool constructor with

[jira] Commented: (DBCP-215) DBCP's initialSize doesn't work as expected

[ https://issues.apache.org/jira/browse/DBCP-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488264 ] Phil Steitz commented on DBCP-215: -- I agree that the BasicDataSourceFactory should return an initialized pool, based

[jira] Updated: (DBCP-215) DBCP's initialSize doesn't work as expected

[ https://issues.apache.org/jira/browse/DBCP-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-215: - Fix Version/s: 1.3 Affects Version/s: 1.2.2 DBCP's initialSize doesn't work as expected

[jira] Updated: (DBCP-214) Basic datasource should respect the context classloader

[ https://issues.apache.org/jira/browse/DBCP-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-214: - Fix Version/s: 1.3 Patches welcome Basic datasource should respect the context classloader

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488252 ] Phil Steitz commented on DBCP-212: -- Thanks, Marcos. Really appreciate your feedback and help chasing this down. I

[jira] Updated: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-212: - Fix Version/s: 1.3 PoolingDataSource closes physical connections

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487994 ] Phil Steitz commented on DBCP-212: -- Thanks. By adding the System.out, I can reproduce the symptoms. You are

[jira] Commented: (DBCP-213) DBCP causes tomcat to hang under moderate load

[ https://issues.apache.org/jira/browse/DBCP-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487486 ] Phil Steitz commented on DBCP-213: -- Thanks for the info. You should run pool 1.3 with DBCP 1.2.2, but that is not

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487488 ] Phil Steitz commented on DBCP-212: -- After running against instrumented dbcp and pool jars and different db engines,

[jira] Commented: (DBCP-213) DBCP causes tomcat to hang under moderate load

[ https://issues.apache.org/jira/browse/DBCP-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487461 ] Phil Steitz commented on DBCP-213: -- What versions of commons-dbcp and commons-pool are your running? DBCP causes

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487203 ] Phil Steitz commented on DBCP-212: -- Can you please provide a little more information on what exactly you are seeing

[jira] Commented: (DBCP-212) PoolingDataSource closes physical connections

[ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487282 ] Phil Steitz commented on DBCP-212: -- Thanks. Also thanks in advance for running against pool 1.2/dbcp 1.2.1 to

[jira] Commented: (DBCP-146) [dbcp] Invalidate broken connections by monitoring SQLExceptions

[ https://issues.apache.org/jira/browse/DBCP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487305 ] Phil Steitz commented on DBCP-146: -- Yes, the patch is against the old cvs repo and older versions of the files. If

[jira] Resolved: (DBCP-68) [dbcp] Commons Collection dependency version clash when using Commons DBCP via Maven2

[ https://issues.apache.org/jira/browse/DBCP-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-68. - Resolution: Fixed 1.2.2 has (at last) been released. [dbcp] Commons Collection dependency version clash

[jira] Commented: (MATH-163) The evaluate method and the getResult method of class Variance give different results

[ https://issues.apache.org/jira/browse/MATH-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485920 ] Phil Steitz commented on MATH-163: -- Thanks for reporting this. I agree with Rory that the spirit of IEEE754 (which

[jira] Updated: (DBCP-210) Have dbcp close pooled prepared statements after some settable time limit

[ https://issues.apache.org/jira/browse/DBCP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-210: - Fix Version/s: 1.3 This is sort of a consequence of pooling prepared statements, so an argument could be

[jira] Commented: (DBCP-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?

[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467235 ] Phil Steitz commented on DBCP-209: -- The problem with getConnection(user, pass) is that this call makes it look

[jira] Updated: (DBCP-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?

[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-209: - Fix Version/s: 1.3 Is DataSource.getConnection(user, pass) working the way it is suppose to?

[jira] Commented: (DBCP-209) Is DataSource.getConnection(user, pass) working the way it is suppose to?

[ https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467241 ] Phil Steitz commented on DBCP-209: -- Yes, that makes sense, but the way to do it is to have the application set

[jira] Commented: (DBCP-208) URL Parsing Bug

[ https://issues.apache.org/jira/browse/DBCP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466360 ] Phil Steitz commented on DBCP-208: -- DBCP should just pass the URL unchanged to the driver's connect() method. Can

[jira] Commented: (DBCP-201) Statement closing due to unprovoked rollback

[ https://issues.apache.org/jira/browse/DBCP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466362 ] Phil Steitz commented on DBCP-201: -- What versions of DBCP and Pool are you running? Statement closing due to

[jira] Updated: (DBCP-201) Statement closing due to unprovoked rollback

[ https://issues.apache.org/jira/browse/DBCP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-201: - Fix Version/s: 1.3 Affects Version/s: (was: 1.3) 1.2.1 Statement

[jira] Updated: (DBCP-205) Intermittently getting Could not retrieve connection info from pool when under load

[ https://issues.apache.org/jira/browse/DBCP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-205: - Fix Version/s: 1.3 Affects Version/s: (was: 1.2.1) (was: Nightly

[jira] Updated: (DBCP-207) DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...))

[ https://issues.apache.org/jira/browse/DBCP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-207: - Fix Version/s: 1.3 DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...))

[jira] Updated: (DBCP-110) [dbcp] Problem reported at forum.java.sun.com

[ https://issues.apache.org/jira/browse/DBCP-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-110: - Fix Version/s: 1.3 [dbcp] Problem reported at forum.java.sun.com

[jira] Updated: (DBCP-208) URL Parsing Bug

[ https://issues.apache.org/jira/browse/DBCP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-208: - Fix Version/s: 1.3 URL Parsing Bug --- Key: DBCP-208 URL:

[jira] Resolved: (DBCP-65) [dbcp] Deadlock when evicting dbcp objects (testWhileIdle=true)

[ https://issues.apache.org/jira/browse/DBCP-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-65. - Resolution: Fixed Fix Version/s: (was: 1.3) 1.2.2 Synchronization was removed

[jira] Resolved: (DBCP-202) Deadlock creating/closing PreparedStatement

[ https://issues.apache.org/jira/browse/DBCP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved DBCP-202. -- Resolution: Fixed Fix Version/s: (was: 1.3) 1.2.2 Fixed in r498524 by

[jira] Updated: (DBCP-128) [dbcp] BasicDataSource.getConnection() Connections don't work as hashtable keys -- test case provided

[ https://issues.apache.org/jira/browse/DBCP-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz updated DBCP-128: - Fix Version/s: (was: 1.3) 1.2.2 [dbcp] BasicDataSource.getConnection() Connections

[jira] Commented: (DBCP-44) [dbcp] Evictor thread in GenericObjectPool has potential for deadlock

[ http://issues.apache.org/jira/browse/DBCP-44?page=comments#action_12460095 ] Phil Steitz commented on DBCP-44: - After looking at the deadlock traces and analyzing the code some more, I think that the root of the problem in this case is

[jira] Commented: (DBCP-65) [dbcp] Deadlock when evicting dbcp objects (testWhileIdle=true)

[ http://issues.apache.org/jira/browse/DBCP-65?page=comments#action_12460140 ] Phil Steitz commented on DBCP-65: - Unless someone can give a good reason that PoolingConnection's prepareStatement methods *must* be synchronized, I am inclined to

[jira] Created: (DBCP-206) DBCP high performance contention point

DBCP high performance contention point --- Key: DBCP-206 URL: http://issues.apache.org/jira/browse/DBCP-206 Project: Commons Dbcp Issue Type: Bug Affects Versions: 1.2.1 Environment: Java 5,

[jira] Commented: (COMMONSSITE-13) Create a timeout so runaway apps get cut off

[ http://issues.apache.org/jira/browse/COMMONSSITE-13?page=comments#action_12459769 ] Phil Steitz commented on COMMONSSITE-13: The problem, I take it, is that builds are hanging. Other than kludgy stuff like running commands in the

[jira] Commented: (DBCP-204) BasicDataSource doesn't include CallableStatement Pooling

[ http://issues.apache.org/jira/browse/DBCP-204?page=comments#action_12459773 ] Phil Steitz commented on DBCP-204: -- Patch looks good. Thanks! We will want to add some test cases. BasicDataSource doesn't include CallableStatement Pooling

[jira] Resolved: (MATH-162) update to mantissa 7.0

[ http://issues.apache.org/jira/browse/MATH-162?page=all ] Phil Steitz resolved MATH-162. -- Resolution: Fixed Patch applied. Thanks! update to mantissa 7.0 -- Key: MATH-162 URL:

[jira] Commented: (DBCP-205) Intermittently getting Could not retrieve connection info from pool when under load

[ http://issues.apache.org/jira/browse/DBCP-205?page=comments#action_12457146 ] Phil Steitz commented on DBCP-205: -- Do you see anything in the Windows event log on the SQL Server box? Is Tomcat running on the same box? That error could

[jira] Commented: (DBCP-193) BasicDataSource returns negative values for NumActive when Oracle Driver Connection#isClosed return true (End of file communication on CHannel)

[ http://issues.apache.org/jira/browse/DBCP-193?page=comments#action_12457147 ] Phil Steitz commented on DBCP-193: -- No (Hen), I think this remains a problem and will be fixed when we fix close semantics in 1.3 BasicDataSource returns

[jira] Resolved: (DBCP-189) [dbcp] Threads do not get a Connection in FIFO mode

[ http://issues.apache.org/jira/browse/DBCP-189?page=all ] Phil Steitz resolved DBCP-189. -- Resolution: Won't Fix The dbcp API makes no commitments regarding preserving invariants of the underlying pool, other than that the exposed parameters work as

[jira] Resolved: (DBCP-195) Bad performance in PoolableConnectionFactory

[ http://issues.apache.org/jira/browse/DBCP-195?page=all ] Phil Steitz resolved DBCP-195. -- Resolution: Duplicate This is a duplicate of DBCP-102, which has been fixed. Bad performance in PoolableConnectionFactory

[jira] Updated: (DBCP-194) BasicDataSource.setLogWriter should not do createDataSource

[ http://issues.apache.org/jira/browse/DBCP-194?page=all ] Phil Steitz updated DBCP-194: - Fix Version/s: 1.3 This will be part of the logging cleanup in 1.3 BasicDataSource.setLogWriter should not do createDataSource

[jira] Updated: (DBCP-202) Deadlock creating/closing PreparedStatement

[ http://issues.apache.org/jira/browse/DBCP-202?page=all ] Phil Steitz updated DBCP-202: - Fix Version/s: 1.3 Affects Version/s: 1.2.2 (was: 1.3) Deadlock creating/closing PreparedStatement

[jira] Resolved: (DBCP-172) [dbcp] Allow for database clusters/clustering

[ http://issues.apache.org/jira/browse/DBCP-172?page=all ] Phil Steitz resolved DBCP-172. -- Resolution: Incomplete The link in the description does not work and it is unclear what is meant in the description. [dbcp] Allow for database

[jira] Updated: (DBCP-203) Want to provide a ClassLoader for BasicDataSource to use for loading a JDBC driver.

[ http://issues.apache.org/jira/browse/DBCP-203?page=all ] Phil Steitz updated DBCP-203: - Fix Version/s: 1.3 Affects Version/s: 1.2.1 Seems like a reasonable enhancement to be included in 1.3. Want to provide a ClassLoader for BasicDataSource to

[jira] Updated: (DBCP-204) BasicDataSource doesn't include CallableStatement Pooling

[ http://issues.apache.org/jira/browse/DBCP-204?page=all ] Phil Steitz updated DBCP-204: - Fix Version/s: 1.3 Affects Version/s: 1.2.1 Patches welcome! BasicDataSource doesn't include CallableStatement Pooling

  1   2   3   >