[ http://jira.jboss.com/jira/browse/JBAS-1424?page=history ]
Adrian Brock moved JBJCA-1 to JBAS-1424:
----------------------------------------
Project: JBoss Application Server (was: JBoss JCA)
Key: JBAS-1424 (was: JBJCA-1)
Component: JCA service
> Force closing of all database connections
> -----------------------------------------
>
> Key: JBAS-1424
> URL: http://jira.jboss.com/jira/browse/JBAS-1424
> Project: JBoss Application Server
> Type: Feature Request
> Components: JCA service
> Reporter: Tom Elrod
> Assignee: Adrian Brock
> Priority: Minor
>
>
> Would like enhancement of the JBossManagedConnectionPool's flush() method to
> not only close those connections in the pool, but also mark those in use so
> that when they are returned to the pool, they are closed as well. Just using
> idle-timeout-minutes is not enough in certain casess as wehn under heavy
> load, as connections may not be idle long enough to be picked up and closed.
> One particular use case for needing this feature is when using plsql, which
> when updated on the server, will cause errors when the same open connection
> is used after this update (so need to close and re-open the connections).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
