Hi All Users. I am repeating a same issue, already having so many lads, due to lock of the thread.
The Name :ejb:/HelloWorldSessionBean//HelloWorldBean!com.ibytecode.kr.business.HelloWorld
Sep 15, 2013 3:17:49 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 1.0.10.Final-redhat-1
Sep 15, 2013 3:17:49 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.4.GA-redhat-1
Sep 15, 2013 3:17:49 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
Sep 15, 2013 3:17:49 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.8.GA-redhat-1
Sep 15, 2013 3:17:49 AM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
INFO: EJBCLIENT000017: Received server version 1 and marshalling strategies [river]
Sep 15, 2013 3:17:49 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@5228b636, receiver=Remoting connection EJB receiver [connection=Remoting connection <6579b32a>,channel=jboss.ejb,nodename=b4l-1f7xlv1]} on channel Channel ID de984deb (outbound) of Remoting connection 6e059e40 to /127.0.0.1:4447
Sep 15, 2013 3:17:49 AM org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver handleMessage
WARN: Unsupported message received with header 0xffffffff
java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:HelloWorldSessionBean, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@ae9ecc8
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:588)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at com.sun.proxy.$Proxy0.sayHello(Unknown Source)
at com.ibytecode.kr.client.EJBApplicationClient.main(EJBApplicationClient.java:16
Hi ....All,
Even though I am not new to EJB and Jboss, but after a long time I am using again this stuffs. So I have been trying to create a EJB 3.0 session bean and deployed on Jboss EAP 6. successfully by help of some example code available on google.
Now trying to access the EJB, by writting an client application. and Its a just demo application for HelloWorld.
Till I have done :
Bean class
Remote interface
Client class(main method)
jboss-ejb-client.properties file in classpath
Could you please help the actual root cause of this ? I have found some guys mentioned like changes of :
1. First option .................
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=127.0.0.1
remote.connection.default.port = 4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.default.username=satyajit
remote.connection.default.password=satyajit@123
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.factory.url.pkgs=org.jboss.ejb.client.naming
java.naming.provider.url=remote://localhost:4447
2. Second Option..........
properties.put("jboss.naming.client.ejb.context", true);
properties.put(Context.URL_PKG_PREFIXES, PKG_INTERFACES);
3. 3rd Option .............
properties file in classpath(checked again even though it was.....)
4. 4th Option............
By adding jboss-client.jar to classpath........
But still I am having same Error.............So don't guess Please...it will create confusion.................if you know clearly please mentioned...........???????
