InvokerLocator already exists for listener

[dunks80]

Does anyone know what this stack trace is about? I'm looping through a list of items and sending each item in the list off to a queue that has an MDB listening on it. I get maybe half way through the list and then this exception occurs. The code worked fine with JbossMQ but when I switched to JBoss messaging this started happening.

javax.jms.IllegalStateException: InvokerLocator already exists for listener id 1436420135. Remove this listener before adding again.
 at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:91)
 at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java:???)
 at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
 at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.invokeNext()Ljava.lang.Object;(ClientConnectionFactoryDelegate$createConnectionDelegate_N6840474864420126404.java:???)
 at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(Ljava.lang.String;Ljava.lang.String;)Lorg.jboss.jms.delegate.ConnectionDelegate;(ClientConnectionFactoryDelegate.java:???)
 at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:202)
 at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:108)
 at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:103)
...

[dunks80]

Sorry I should add that I'm using JBoss 4.0.5.GA and JBoss Messaging 1.0.1.GA
Thanks

[dunks80]

I think I found the problem http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93384

[timfox]

dunks80 -

I suggest you post a bug report in JIRA for JBoss Remoting for this one.

[tom.elrod]

Per the related discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984654#3984654 and associated jira issue, the callback behavior has been modified. Please let me know if behavior change covered in other forum thread is going to be an issue.

[ron_sigal]

The following change has been made to the behavior of reused InvokerCallbackHandlers:

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.