[JBoss JIRA] Resolved: (JBAS-3033) Throttle creation of new connections
by Weston Price (JIRA)
[ 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
19 years, 2 months
[JBoss JIRA] Deleted: (JBAS-4145) Update to JacORB 2.3.0.GA
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4145?page=all ]
Dimitris Andreadis deleted JBAS-4145:
-------------------------------------
> Update to JacORB 2.3.0.GA
> -------------------------
>
> Key: JBAS-4145
> URL: http://jira.jboss.com/jira/browse/JBAS-4145
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Fernando Nasser
>
> We are currently using a locally patches JacORB 2.2.4.
> The 2.30.GA includes our patch and also has some other fixes as well.
> From Francisco Reverbel:
> Yes, that patch is in JacORB 2.3.0, which includes at least another
> RMI-related fix as well. It would be good to upgrade. (Disclaimer: I have
> never tested JacORB 2.3.0 with JBossAS. A full run of the iiop testsuite
> is needed.)
> Notice that JacORB 2.3.0 has a "new property interop.sun to fix RMI/IIOP
> related interoperability issues". Perhaps this makes a difference with
> respect to the iiop testcase that has been recently disabled on JDK1.5...
--
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
19 years, 2 months