Introduce a max wait parameter in the jdbc-ng connection pool
-------------------------------------------------------------
Key: GEOT-2298
URL: http://jira.codehaus.org/browse/GEOT-2298
Project: GeoTools
Issue Type: Improvement
Components: data jdbc-ng
Affects Versions: 2.5.2
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.5.3
The connection pools are setup without specifying a max wait parameter, which
tells dbcp how much time to wait for a new connection request.
The default is -1, which means waiting indefinitely.
Now, with Oracle, if the server decides you're not allowed to any more
connection, you effectively lock up GeoServer completely.
The max wait should be configurable by the user, as it will affect how requests
under heavily load are dropped, but we should have a non null default too, so
that the UI won't lock up. Say, 10 seconds?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
