|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
23/Jul/07 10:29 PM
|
|
Suppose there are several connections being used now by different servlets. calling the basicDataSource,close() does not have any impact on the connection pool. I expect that after these servlet return the connections the pool should be shut down immediately. I also expect that any more requests to borrow connections from the pool should not be fulfilled. However, my experiment does not seem to support my expectations. Calling basicDataSource.close() seems to be ignored while there are connections being used.
|
|
Description
|
Suppose there are several connections being used now by different servlets. calling the basicDataSource,close() does not have any impact on the connection pool. I expect that after these servlet return the connections the pool should be shut down immediately. I also expect that any more requests to borrow connections from the pool should not be fulfilled. However, my experiment does not seem to support my expectations. Calling basicDataSource.close() seems to be ignored while there are connections being used. |
Show » |
made changes - 11/May/07 04:57 AM
| Field |
Original Value |
New Value |
|
Fix Version/s
|
|
1.3
[ 12311977
]
|
made changes - 23/Jul/07 10:29 PM
|
Assignee
|
|
Dain Sundstrom
[ dain
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
made changes - 25/Mar/08 08:11 AM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Bug
Closed
Major
How to close the connection pool without shutting down the JVM while there are connections being used?
