[jboss-jira] [JBoss JIRA] Closed: (JBREM-523) connection pool on socket client invoker needs to be bound
David Lloyd (JIRA)
jira-events at lists.jboss.org
Wed Sep 26 05:31:32 EDT 2007
[ http://jira.jboss.com/jira/browse/JBREM-523?page=all ]
David Lloyd closed JBREM-523.
-----------------------------
> connection pool on socket client invoker needs to be bound
> ----------------------------------------------------------
>
> Key: JBREM-523
> URL: http://jira.jboss.com/jira/browse/JBREM-523
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: transport
> Affects Versions: 2.0.0.Beta2 (Boon)
> Reporter: Tom Elrod
> Assigned To: Tom Elrod
> Fix For: 2.0.0.CR1 (Boon)
>
>
> The SocketClientInvoker (more correctly, the MicroSocketClientInvoker), has a client socket connection pool, but does not limit the number the client socket connections created to the max pool size. Instead, if max pool size + 1 invocations are made, the client invoker will create a new client socket connection, make its invocation, and throw the connection away instead of putting into the pool when done. Problem with this is that if make a lot of concurrent client invocations at same time, the number of client socket connections can be huge. Therefore, need to make the pool bound so that max pool size will be the max number of client socket connections allowed. If more concurrent invocations exists than number of max pool size, the extra invocations will have to wait for a connection to be put back in the pool (or timeout and throw exception).
--
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
More information about the jboss-jira
mailing list