[jboss-jira] [JBoss JIRA] Resolved: (JBAS-3033) Throttle creation of new connections
[ http://jira.jboss.com/jira/browse/JBAS-3033?page=all ]
Weston Price resolved JBAS-3033.
--------------------------------
Resolution: Rejected
This behavior is already in place. The semaphore controlling access to the pool provides
for the wait time and connection creation behavior. If a connection is unavaliable a wait
time configured as (blocking-timeout-millis) will control access until a permit is
released.
This is not applicable to JMS inflow as this is controlled by the number of max sessions
for the JMS ServerSession pool and has nothing to do with the
InternalManagedConnectionPool used for outbound connectivity.
Throttle creation of new connections
------------------------------------
Key: JBAS-3033
URL: http://jira.jboss.com/jira/browse/JBAS-3033
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JCA service
Reporter: Elias Ross
When a pooled connection is not available, the connection pool creates an additional
connection with no waiting, up to the maximum allowed size. What tends to happen with many
worker threads is the DB pool grows very quickly.
It would be nice to have a settable property with the following behavior:
0. if there is an available connection, return it
1. poll() for N seconds for a recently returned connection, if one arrives in N seconds,
return it
2. else, create a new connection
For JMS connections, this would be useful for keeping the server from creating the
maximum number of MDB right away and ballooning memory.
Additionally (and perhaps as a different bug), the BasicThreadPool should have this sort
of property as well.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira