This content has been marked as final.
Show 5 replies
-
1. Re: InvokerLocator already exists for listener
dunks80 Oct 25, 2006 10:54 AM (in response to dunks80)Sorry I should add that I'm using JBoss 4.0.5.GA and JBoss Messaging 1.0.1.GA
Thanks -
2. Re: InvokerLocator already exists for listener
dunks80 Oct 26, 2006 7:17 AM (in response to dunks80)I think I found the problem http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93384
-
3. Re: InvokerLocator already exists for listener
timfox Oct 30, 2006 5:56 AM (in response to dunks80)dunks80 -
I suggest you post a bug report in JIRA for JBoss Remoting for this one. -
4. Re: InvokerLocator already exists for listener
tom.elrod Nov 9, 2006 3:51 PM (in response to dunks80)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.
-
5. Re: InvokerLocator already exists for listener
ron_sigal Dec 6, 2006 11:32 PM (in response to dunks80)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.