[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Non connected remoting clients throwing java.lang.Except
timfox
do-not-reply at jboss.com
Sat Jan 20 14:13:47 EST 2007
Hmmm, this:
| Can not make remoting client invocation due to not being connected to server.
| at org.jboss.remoting.Client.invoke(Client.java:639)
| at org.jboss.remoting.Client.invoke(Client.java:627)
| at org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:118)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_N5002091796089334799.invokeNext(ClientSessionDelegate$createConsumerDelegate_N5002091796089334799.java)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:153)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect17.invoke(StateCreationAspect17.java)
| at
|
Looks very much like another remoting bug I have replicated here:
http://jira.jboss.com/jira/browse/JBMESSAGING-765
I believe it is a bug in the way remoting handles reference counts for invokers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004356#4004356
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004356
More information about the jboss-dev-forums
mailing list