[jboss-jira] [JBoss JIRA] Commented: (JBREM-622) InvokerLocator already exists for listener
Tom Elrod (JIRA)
jira-events at jboss.com
Thu Nov 9 15:50:41 EST 2006
[ http://jira.jboss.com/jira/browse/JBREM-622?page=comments#action_12346621 ]
Tom Elrod commented on JBREM-622:
----------------------------------
Behavior - If doing pull callbacks, can have same callback handler registered with two remoting Client instances (i.e. A and B) and the server will see this as two distinct callback listeners being registered. So if server generates a callback, both Client instance will retreive a callback.
If doing push callbacks, meaning have a callback server registered to receive callbacks, the callbacks will be tied to that callback server and its callback handler. Therefore, if have callback handler and server registered, only one callback will be delivered per one generated on target server, regardless of with how many remoting Clients they have been registered as listeners with. An example would be have remoting Client A and B, and have callback handler X and callback server Y. If registered callback handler X and callback server Y with both A and B and the server generates a callback message, it will only be delivered once to callback handler X.
If have the same callback handler registered with multiple callback server, a callback message will be delivered for each callback server. For example, if have callback handler X and callback server Y and Z and then register callback handler X twixe (once with Y and once with Z), then will be delivered the same callback message twice (once by Y and once by Z).
When a callback handler is removed and are using push callbacks, the callback handler will be removed as a listener from all callback servers it has been registered under.
> 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
More information about the jboss-jira
mailing list