[jaikiran]

Thanks for those logs, those helped understand what's going on. The Thread.sleep won't work out now that I relate those logs to the code.

So the only workaround is just using a single receiver/connection for now. I'm implementing a fix for multiple receivers/connections and will let you know once it's ready.

[morphy]

glad to help because your work helps me

[jaikiran]

I've deployed a snapshot which should contain a fix for your multiple connections problems. Download this jar https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/jboss-ejb-client/1.0.0.Beta8-SNAPSHOT/jboss-ejb-client-1.0.0.Beta8-20111125.161426-1.jar and replace the jboss-ejb-client 1.0.0.Beta7 on your client classpath with this new one. Let me know how it goes.

[morphy]

doing right now.... thnx

[morphy]

No... it doesn't work (sources still have the thread sleep and the dependency has been changed only in the client side), feel free to use me for testing.... and feel free to use private messages if you don't wont to spam the thread and feel free to ask my test case if you need local environment... i mean... 100% available to help you:

25-nov-2011 21.37.53 org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.0.Beta8-SNAPSHOT
25-nov-2011 21.38.03 org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.0.CR4
25-nov-2011 21.38.03 org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.0.CR4
25-nov-2011 21.38.03 org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.0.CR3
25-nov-2011 21.38.04 org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 1 and marshalling strategies [river, java-serial]
25-nov-2011 21.38.04 org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context org.jboss.ejb.client.EJBReceiverContext@68f51766 on channel Channel ID e940c778 (outbound) of Remoting connection 1d30b5e2 to /127.0.0.1:4547
25-nov-2011 21.38.04 org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: Received server version 1 and marshalling strategies [river, java-serial]
25-nov-2011 21.38.04 org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: Successful version handshake completed for receiver context org.jboss.ejb.client.EJBReceiverContext@49c88f2b on channel Channel ID 860ae03c (outbound) of Remoting connection 6153e0c0 to /127.0.0.1:4647
[WARNING] 
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:TestRemoteBean,distinctname:] combination
        at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:236)
        at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:95)
        at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:86)
        at $Proxy14.sayHello(Unknown Source)
        at com.hp.dragon.test.TheApp.run(TheApp.java:64)
        at com.hp.dragon.test.TheApp.main(TheApp.java:35)
        ... 6 more