[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed DBCP-595.
Resolution: Not A Problem
Don't mean to be blunt / dismissive with the close here. But this does not
look
[
https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-590.
--
Fix Version/s: 2.11.1
Resolution: Fixed
I am really sorry it took me so long to figure this out.
[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816813#comment-17816813
]
Phil Steitz edited comment on DBCP-595 at 2/12/24 11:28 PM:
I just realized
[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816813#comment-17816813
]
Phil Steitz edited comment on DBCP-595 at 2/12/24 11:27 PM:
I just realized
[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816813#comment-17816813
]
Phil Steitz commented on DBCP-595:
--
I just realized there is another scenario that can lead to this, which
[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816685#comment-17816685
]
Phil Steitz commented on DBCP-595:
--
Thanks for the info on validation. That info and the partial thread
[
https://issues.apache.org/jira/browse/DBCP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816463#comment-17816463
]
Phil Steitz commented on DBCP-595:
--
I am still working through the repro code, but the symptoms don't make
[
https://issues.apache.org/jira/browse/POOL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772042#comment-17772042
]
Phil Steitz commented on POOL-413:
--
One option to consider here is to use the native capacity management
[
https://issues.apache.org/jira/browse/POOL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772023#comment-17772023
]
Phil Steitz commented on POOL-413:
--
Thanks for reporting this. The analysis looks correct to me. It is
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-411.
> NPE when deregistering key at end of borrow
> ---
>
>
[
https://issues.apache.org/jira/browse/POOL-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-408.
> A typo of KeyedPooledObjectFactory on the site and Javadoc
>
[
https://issues.apache.org/jira/browse/POOL-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-409.
> BasicDataSource should support GenericObjectPool->getStatsString()
>
[
https://issues.apache.org/jira/browse/POOL-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-402.
> Check blockWhenExhausted in hasBorrowWaiters
>
>
>
[
https://issues.apache.org/jira/browse/POOL-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-394.
> GenericKeyedObjectPool doesn't have getKeys() implemented
>
[
https://issues.apache.org/jira/browse/POOL-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-405.
> NullPointerException at
>
[
https://issues.apache.org/jira/browse/POOL-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-393.
> BaseGenericObjectPool.jmxRegister may cost too much time
>
[
https://issues.apache.org/jira/browse/POOL-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-391.
> GenericKeyedObjectPool is not thread safe when invoke method `borrowObject`
> and `destroy` simultaneously
>
[
https://issues.apache.org/jira/browse/POOL-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-242.
Resolution: Not A Problem
> Set thread name for EvictionTimer
> -
>
>
[
https://issues.apache.org/jira/browse/POOL-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-299:
-
Fix Version/s: 3.0
> testOnBorrow overrides testOnCreate=false, add testOnReuse to complement
>
[
https://issues.apache.org/jira/browse/POOL-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-325:
-
Fix Version/s: 3.0
> testOnReturn() available as asynchronous
>
>
[
https://issues.apache.org/jira/browse/POOL-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-381.
Resolution: Not A Problem
> Race condition in the GenericObjectPool in removeAbandoned functionality
>
[
https://issues.apache.org/jira/browse/POOL-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-238:
-
Fix Version/s: 2.13
> Improve test generics
> -
>
> Key: POOL-238
>
[
https://issues.apache.org/jira/browse/POOL-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-353:
-
Fix Version/s: (was: 2.12.0)
> Return false if current connection count is less then MinIdle in
>
[
https://issues.apache.org/jira/browse/POOL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-400.
Resolution: Fixed
I do not see the need to bring in a new dependency for this case.
> Refactor
[
https://issues.apache.org/jira/browse/POOL-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-282:
-
Fix Version/s: 2.13
> CLONE - Support AbandonedConfig in SharedPoolDataSource
>
[
https://issues.apache.org/jira/browse/POOL-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-290:
-
Fix Version/s: 2.13
> TestSoftRefOutOfMemory goes into infinite loop
>
[
https://issues.apache.org/jira/browse/POOL-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-351:
-
Fix Version/s: 3.0
> Add JMX Notifications for NumActive and NumIdle
>
[
https://issues.apache.org/jira/browse/POOL-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-305:
-
Fix Version/s: 3.0
> Add maxAge to pool config
> -
>
> Key:
[
https://issues.apache.org/jira/browse/POOL-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-321:
-
Fix Version/s: 3.0
(was: 2.12.0)
> ObjectPool.addObject limiting us to add an
[
https://issues.apache.org/jira/browse/POOL-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-267:
-
Fix Version/s: 2.13
(was: 2.12.0)
> Use of AbandonListener instead of PrintWriter
[
https://issues.apache.org/jira/browse/POOL-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-272:
-
Fix Version/s: 2.13
(was: 2.12.0)
> GenericKeyedObjectPool should have a per-key
[
https://issues.apache.org/jira/browse/POOL-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-406:
-
Fix Version/s: 3.0
> add support for Micrometer
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/POOL-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-372:
-
Fix Version/s: 3.0
> CallStackUtils mishandles security manager check part 2
>
[
https://issues.apache.org/jira/browse/POOL-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-401:
-
Fix Version/s: 2.13
> GKOP invalidateObject should make capacity available to all keyed pools
>
[
https://issues.apache.org/jira/browse/POOL-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-407:
-
Fix Version/s: 3.0
> Threads get stuck when idleObjects list is empty.
>
[
https://issues.apache.org/jira/browse/POOL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-410:
-
Fix Version/s: 2.13
> EHN Max Concurrent Connections in Stats
> ---
>
[
https://issues.apache.org/jira/browse/POOL-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-350:
-
Fix Version/s: 2.13
> Add option for not executing "hasBorrowWaiters()" while returning objects
>
[
https://issues.apache.org/jira/browse/POOL-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-269:
-
Fix Version/s: 3.0
(was: 2.12.0)
> Use generic exceptions instead of
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved POOL-411.
--
Resolution: Fixed
> NPE when deregistering key at end of borrow
>
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749423#comment-17749423
]
Phil Steitz commented on POOL-411:
--
Fully fixed in 980aae56bf732178a9e02a3cb686f0104bffb6d3.
The problem
[
https://issues.apache.org/jira/browse/POOL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743558#comment-17743558
]
Phil Steitz commented on POOL-410:
--
Moving a comment from PR to here. I think I now understand at least
[
https://issues.apache.org/jira/browse/POOL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743460#comment-17743460
]
Phil Steitz commented on POOL-410:
--
This looks more like a question for the user list. For monitoring,
[
https://issues.apache.org/jira/browse/POOL-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742216#comment-17742216
]
Phil Steitz commented on POOL-407:
--
Looking more carefully at this, the sequence in the description can
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741435#comment-17741435
]
Phil Steitz commented on POOL-411:
--
[~sebb] I added sleeps temporarily between the locks in
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741331#comment-17741331
]
Phil Steitz edited comment on POOL-411 at 7/8/23 9:16 PM:
--
[~sebb] I am not sure I
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741331#comment-17741331
]
Phil Steitz commented on POOL-411:
--
[~sebb] I am not sure I understand your last comment. With the test
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741220#comment-17741220
]
Phil Steitz commented on POOL-411:
--
[~ggregory] - looks great. Great idea to use computeIfAbsent and to
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741156#comment-17741156
]
Phil Steitz commented on POOL-411:
--
If I make the following changes to testConcurrentBorrowAnd clear, the
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741106#comment-17741106
]
Phil Steitz edited comment on POOL-411 at 7/7/23 3:50 PM:
--
[~sebb] - thanks for
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741106#comment-17741106
]
Phil Steitz commented on POOL-411:
--
[~sebb] - thanks for looking at this. You are right - the scenario I
[ https://issues.apache.org/jira/browse/POOL-411 ]
Phil Steitz deleted comment on POOL-411:
--
was (Author: psteitz):
The added test case has failed at least once now. I think there is a problem
with register/deregister protection of pools. Very
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened POOL-411:
--
The added test case has failed at least once now. I think there is a problem
with register/deregister
[
https://issues.apache.org/jira/browse/DBCP-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738305#comment-17738305
]
Phil Steitz commented on DBCP-591:
--
Acknowledged. It is strange that intrinsic locks work differently,
[
https://issues.apache.org/jira/browse/IO-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732273#comment-17732273
]
Phil Steitz commented on IO-802:
[~ggregory] Makes sense. Thanks.
> Restore threadlocal for skipfully()
[
https://issues.apache.org/jira/browse/IO-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732238#comment-17732238
]
Phil Steitz commented on IO-802:
I agree that it would be best to just add back the protection, for the
[
https://issues.apache.org/jira/browse/POOL-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729462#comment-17729462
]
Phil Steitz commented on POOL-412:
--
Yes, I would close this.
> [GenericKeyedObjectPool] ensureMinIdle not
[
https://issues.apache.org/jira/browse/POOL-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729430#comment-17729430
]
Phil Steitz commented on POOL-412:
--
This is an interesting use case. Honestly, I think GKOP is working as
[
https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681805#comment-17681805
]
Phil Steitz edited comment on DBCP-590 at 1/30/23 2:18 AM:
---
I will look more at
[
https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681805#comment-17681805
]
Phil Steitz commented on DBCP-590:
--
I will look more at this when I have a little more time, but I suspect
[
https://issues.apache.org/jira/browse/POOL-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653706#comment-17653706
]
Phil Steitz commented on POOL-401:
--
It looks to me that at least as of 2.11.1 reuseCapacity is called on
[
https://issues.apache.org/jira/browse/POOL-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653705#comment-17653705
]
Phil Steitz commented on POOL-407:
--
Thanks for reporting this with the detailed analysis. It is a
[
https://issues.apache.org/jira/browse/POOL-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653704#comment-17653704
]
Phil Steitz commented on POOL-350:
--
Any feedback on the reuseCapacityOnReturn, reuseCapacityOnMaintenance
[
https://issues.apache.org/jira/browse/POOL-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653703#comment-17653703
]
Phil Steitz commented on POOL-372:
--
I am not a security expert, so I can't comment on the assertion in (b)
[
https://issues.apache.org/jira/browse/POOL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653699#comment-17653699
]
Phil Steitz commented on POOL-264:
--
The entire setup was changed in 2.0. Unless someone wants to take up
[
https://issues.apache.org/jira/browse/DBCP-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622847#comment-17622847
]
Phil Steitz commented on DBCP-587:
--
Thanks. It was a good question.
> DBCP and Transparent
[
https://issues.apache.org/jira/browse/DBCP-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619934#comment-17619934
]
Phil Steitz commented on DBCP-587:
--
GenericObjectPool has no initialSize parameter. You need to do what
[
https://issues.apache.org/jira/browse/POOL-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531339#comment-17531339
]
Phil Steitz edited comment on POOL-282 at 5/3/22 6:08 PM:
--
[~ashok2ashok]
First,
[
https://issues.apache.org/jira/browse/POOL-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531339#comment-17531339
]
Phil Steitz commented on POOL-282:
--
[~ashok2ashok]
First, many thanks for stepping up to the challenge
[
https://issues.apache.org/jira/browse/DBCP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17530947#comment-17530947
]
Phil Steitz commented on DBCP-585:
--
[~ggregory] yes this looks good
> Connection level JMX queries
[
https://issues.apache.org/jira/browse/DBCP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526928#comment-17526928
]
Phil Steitz commented on DBCP-585:
--
[~ggregory] sorry I missed this. There is a small javadoc error in
[
https://issues.apache.org/jira/browse/DBCP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520227#comment-17520227
]
Phil Steitz commented on DBCP-585:
--
Nice analysis. The patch looks reasonable as a way to turn off the
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-404.
Resolution: Not A Problem
We can open an enhancement request to add global pool management, but I do not
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481215#comment-17481215
]
Phil Steitz commented on POOL-404:
--
[~ggregory] Can you see a scenario where multiple evictors can be
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480744#comment-17480744
]
Phil Steitz commented on POOL-404:
--
[~patrickjamesbarry] That is interesting. Could be we actually have a
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480706#comment-17480706
]
Phil Steitz commented on POOL-404:
--
Yes that is what I meant by the closeAll option. Still seems a little
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480250#comment-17480250
]
Phil Steitz edited comment on POOL-404 at 1/22/22, 5:26 PM:
That would have to
[
https://issues.apache.org/jira/browse/POOL-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480250#comment-17480250
]
Phil Steitz commented on POOL-404:
--
That would have to be a *global* JVM-level close that would not be
[
https://issues.apache.org/jira/browse/POOL-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454139#comment-17454139
]
Phil Steitz commented on POOL-403:
--
This is being picked up from the KeyedObjectPool interface javadoc. I
[
https://issues.apache.org/jira/browse/POOL-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443194#comment-17443194
]
Phil Steitz edited comment on POOL-393 at 11/14/21, 4:55 PM:
-
I verified that
[
https://issues.apache.org/jira/browse/POOL-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443194#comment-17443194
]
Phil Steitz commented on POOL-393:
--
I verified that with the 2.11.1 code it can take 9+ seconds to
[
https://issues.apache.org/jira/browse/POOL-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443182#comment-17443182
]
Phil Steitz commented on POOL-394:
--
I have not run into this requirement in my own apps, but I can see how
Phil Steitz created POOL-401:
Summary: GKOP invalidateObject should make capacity available to
all keyed pools
Key: POOL-401
URL: https://issues.apache.org/jira/browse/POOL-401
Project: Commons Pool
[
https://issues.apache.org/jira/browse/POOL-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17442354#comment-17442354
]
Phil Steitz commented on POOL-391:
--
A fix for this is in [https://github.com/apache/commons-pool/pull/113]
[
https://issues.apache.org/jira/browse/POOL-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17366264#comment-17366264
]
Phil Steitz commented on POOL-396:
--
Sorry for the slow response. Really nice work on this [~jeremyk-91].
[
https://issues.apache.org/jira/browse/POOL-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364356#comment-17364356
]
Phil Steitz commented on POOL-396:
--
After sleeping on this, I think it is probably better to go ahead and
[
https://issues.apache.org/jira/browse/POOL-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364015#comment-17364015
]
Phil Steitz commented on POOL-396:
--
Nice work on the report and patch. Thanks especially for the unit
[
https://issues.apache.org/jira/browse/DBCP-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-572:
-
Assignee: (was: Phil Steitz)
> timed out connections remain active in the pool
>
[
https://issues.apache.org/jira/browse/DBCP-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291763#comment-17291763
]
Phil Steitz commented on DBCP-572:
--
This is not a bug. By default, the pool does not try to keep
[
https://issues.apache.org/jira/browse/DBCP-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-572:
-
Assignee: Phil Steitz
> timed out connections remain active in the pool
>
[
https://issues.apache.org/jira/browse/POOL-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246147#comment-17246147
]
Phil Steitz commented on POOL-390:
--
Looks like a useful feature to me . DBCP does this in its object
Phil Steitz created DBCP-567:
Summary: Use abort rather than close to clean up abandoned
connections
Key: DBCP-567
URL: https://issues.apache.org/jira/browse/DBCP-567
Project: Commons DBCP
Phil Steitz created POOL-387:
Summary: Object factory destroy method should carry information on
activation context
Key: POOL-387
URL: https://issues.apache.org/jira/browse/POOL-387
Project: Commons Pool
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173949#comment-17173949
]
Phil Steitz edited comment on DBCP-559 at 8/9/20, 6:44 PM:
---
PR is
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173949#comment-17173949
]
Phil Steitz commented on DBCP-559:
--
PR is [here|https://github.com/apache/commons-dbcp/pull/50].
* One
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173447#comment-17173447
]
Phil Steitz edited comment on DBCP-559 at 8/8/20, 5:20 PM:
---
I am working on a PR
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173447#comment-17173447
]
Phil Steitz edited comment on DBCP-559 at 8/8/20, 5:15 PM:
---
I am working on a PR
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173447#comment-17173447
]
Phil Steitz commented on DBCP-559:
--
I am working on a PR with tests for this, though I will happily review
[
https://issues.apache.org/jira/browse/DBCP-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed DBCP-563.
Resolution: Not A Problem
This is a driver bug. I can reproduce using mysql-connector-java-5.x but not
[
https://issues.apache.org/jira/browse/DBCP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166644#comment-17166644
]
Phil Steitz commented on DBCP-559:
--
This looks reasonable to me. The change is just to add an "open"
[
https://issues.apache.org/jira/browse/POOL-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162100#comment-17162100
]
Phil Steitz edited comment on POOL-386 at 7/21/20, 6:04 PM:
A couple things to
1 - 100 of 1998 matches
Mail list logo
