[jboss-jira] [JBoss JIRA] Commented: (JBREM-622) InvokerLocator already exists for listener

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-622?page=comments#action_12348299 ] 
            
Ron Sigal commented on JBREM-622:
---------------------------------

A modification is necessary to one of the behaviors described above.  ServerInvoker stores the client side InvokerCallbackHandler using a key consisting of the sessionId of the Client that is registering the InvokerCallbackHandler concatenated with the InvokerCallbackHandler's listenerId.  When ServerInvoker is asked to unregister a client side InvokerCallbackHandler X, it looks for X based on the sessionId of the Client making the request concatenated with the listenerId of X.   When a Client other than the one that registered InvokerCallbackHandler X tries to unregister X, the ServerInvoker can't find X.   It follows that a Client can unregister only those InvokerCallbackHandlers that it has registered.

> InvokerLocator already exists for listener
> ------------------------------------------
>
>                 Key: JBREM-622
>                 URL: http://jira.jboss.com/jira/browse/JBREM-622
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA (Boon)
>         Environment: JBoss 4.0.5.GA
> JBoss Messaging 1.0.1.GA
> 64-bit Fedora Core 5 
> BEA Jrockit R26.0.0-jdk1.5.0_04_x86_64
>            Reporter: Galen Dunkleberger
>         Assigned To: Tom  Elrod
>             Fix For: 2.2.0.Alpha3 (Bluto), 3.0.0.Alpha1 (Otter)
>
>
> When trying to send many small messsages very quickly through JBoss messaging I was getting the following error
> javax.jms.IllegalStateException: InvokerLocator already exists for listener id 1436420135.  Remove t
> his listener before adding again.
>         at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:91)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6
> 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe
> legate_N6840474864420126404.java:???)
>         at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6
> 840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDe
> legate_N6840474864420126404.java:???)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(Lj
> ava.lang.String;Ljava.lang.String;)Lorg.jboss.jms.delegate.ConnectionDelegate;(ClientConnectionFacto
> ryDelegate.java:???)
>         at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFacto
> ry.java:202)
>         at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.
> java:108)
>         at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.
> java:103)

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