[jira] [Updated] (POOL-189) close() does not release threads blocked on borrowObject()

2011-11-15 Thread William R. Speirs (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William R. Speirs updated POOL-189:
---

Attachment: BUG-189v2.diff

Included changes to GenericKeyedObjectPool and associated test.

 close() does not release threads blocked on borrowObject()
 --

 Key: POOL-189
 URL: https://issues.apache.org/jira/browse/POOL-189
 Project: Commons Pool
  Issue Type: Bug
Affects Versions: 1.5.6
 Environment: java 1.6.0_24
Reporter: Adrian Nistor
 Fix For: 1.5.7

 Attachments: BUG-189v1.diff, BUG-189v2.diff, Test.java


 Hi,
 When I call close() and borrowObject() concurrently with no objects in
 the pool, close() will finish but borrowObject() is blocked forever.
 The documentation of close() mentions that borrowObject() should fail 
 with IllegalStateException, so I would expect the waiting threads to 
 throw IllegalStateException.
 I will attach a test that exposes this problem. For this test, the 
 expected output is:
 0
 1
 2
 ...
 4999
 DONE
 But when the bug manifests (almost always for this test), the output 
 is:
 0
 1
 2
 The test does not finish, it just gets stuck after printing several 
 values.
 Is this a bug or am I reading the documentation wrongly? Is there 
 a patch for this?
 Thanks!
 Adrian

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (POOL-189) close() does not release threads blocked on borrowObject()

2011-11-14 Thread William R. Speirs (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William R. Speirs updated POOL-189:
---

Attachment: BUG-189v1.diff

 close() does not release threads blocked on borrowObject()
 --

 Key: POOL-189
 URL: https://issues.apache.org/jira/browse/POOL-189
 Project: Commons Pool
  Issue Type: Bug
Affects Versions: 1.5.6
 Environment: java 1.6.0_24
Reporter: Adrian Nistor
 Fix For: 1.5.7

 Attachments: BUG-189v1.diff, Test.java


 Hi,
 When I call close() and borrowObject() concurrently with no objects in
 the pool, close() will finish but borrowObject() is blocked forever.
 The documentation of close() mentions that borrowObject() should fail 
 with IllegalStateException, so I would expect the waiting threads to 
 throw IllegalStateException.
 I will attach a test that exposes this problem. For this test, the 
 expected output is:
 0
 1
 2
 ...
 4999
 DONE
 But when the bug manifests (almost always for this test), the output 
 is:
 0
 1
 2
 The test does not finish, it just gets stuck after printing several 
 values.
 Is this a bug or am I reading the documentation wrongly? Is there 
 a patch for this?
 Thanks!
 Adrian

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (POOL-189) close() does not release threads blocked on borrowObject()

2011-11-13 Thread Phil Steitz (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Steitz updated POOL-189:
-

Fix Version/s: 1.5.7

Thanks for reporting this.

 close() does not release threads blocked on borrowObject()
 --

 Key: POOL-189
 URL: https://issues.apache.org/jira/browse/POOL-189
 Project: Commons Pool
  Issue Type: Bug
Affects Versions: 1.5.6
 Environment: java 1.6.0_24
Reporter: Adrian Nistor
 Fix For: 1.5.7

 Attachments: Test.java


 Hi,
 When I call close() and borrowObject() concurrently with no objects in
 the pool, close() will finish but borrowObject() is blocked forever.
 The documentation of close() mentions that borrowObject() should fail 
 with IllegalStateException, so I would expect the waiting threads to 
 throw IllegalStateException.
 I will attach a test that exposes this problem. For this test, the 
 expected output is:
 0
 1
 2
 ...
 4999
 DONE
 But when the bug manifests (almost always for this test), the output 
 is:
 0
 1
 2
 The test does not finish, it just gets stuck after printing several 
 values.
 Is this a bug or am I reading the documentation wrongly? Is there 
 a patch for this?
 Thanks!
 Adrian

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (POOL-189) close() does not release threads blocked on borrowObject()

2011-08-25 Thread Adrian Nistor (JIRA)

 [ 
https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adrian Nistor updated POOL-189:
---

Attachment: Test.java

 close() does not release threads blocked on borrowObject()
 --

 Key: POOL-189
 URL: https://issues.apache.org/jira/browse/POOL-189
 Project: Commons Pool
  Issue Type: Bug
Affects Versions: 1.5.6
 Environment: java 1.6.0_24
Reporter: Adrian Nistor
 Attachments: Test.java


 Hi,
 When I call close() and borrowObject() concurrently with no objects in
 the pool, close() will finish but borrowObject() is blocked forever.
 The documentation of close() mentions that borrowObject() should fail 
 with IllegalStateException, so I would expect the waiting threads to 
 throw IllegalStateException.
 I will attach a test that exposes this problem. For this test, the 
 expected output is:
 0
 1
 2
 ...
 4999
 DONE
 But when the bug manifests (almost always for this test), the output 
 is:
 0
 1
 2
 The test does not finish, it just gets stuck after printing several 
 values.
 Is this a bug or am I reading the documentation wrongly? Is there 
 a patch for this?
 Thanks!
 Adrian

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira