[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-432) One connection per unique JMS server leak

[Clebert Suconic (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=comments#action_12343507 ] 
            
Clebert Suconic commented on JBMESSAGING-432:
---------------------------------------------

Can we just mark won't fix?

A proper fix here would require changes on the API anyway.


> One connection per unique JMS server leak
> -----------------------------------------
>
>                 Key: JBMESSAGING-432
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.0.1.CR2
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.2.1
>
>
> Methods on connection factory are executed in ConnectionFactoryDelegate on their own client.
> This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up.
> This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak.

-- 
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