[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1832) Client.removeListener() should be called before Client.disconnect() is called.

[Yong Hao Gao (JIRA)]

Client.removeListener() should be called before Client.disconnect() is called.
------------------------------------------------------------------------------

                 Key: JBMESSAGING-1832
                 URL: https://jira.jboss.org/browse/JBMESSAGING-1832
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Yong Hao Gao
            Assignee: Yong Hao Gao


(From Ron)
there are a bunch of Remoting threads that are created but not 
> destroyed.  These are BisocketServerInvoker$ControlConnectionThreads.  
> They run on the client and handle "create connection" requests from 
> the server coming in on the control connection.
>
> When org.jboss.remoting.Client.addListener() is called, a 
> BisocketServerInvoker is created on the client side, and a 
> BisocketServerInvoker$ControlConnectionThread is created.  When 
> Client.removeListener() is called, the
> BisocketServerInvoker$ControlConnectionThread is shut down.  But in 
> this case (and it happened in one other support case), the number of 
> BisocketServerInvoker$ControlConnectionThreads just keeps growing.  I 
> created a jboss-remoting.jar with extra logging which shows that 
> JBossMessaging doesn't seem to be calling Client.removeListener() 
> before it calls Client.disconnect().
>


-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira