-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR12
-
None
-
Blocks Testing
-
-
-
-
-
-
-
Upon attempting to invoke method on bean from legacy EJB client standalone application, the following exceptions are produced:
Exception in thread "Remoting "config-based-ejb-client-endpoint" task-5" java.lang.RuntimeException: Client cannot communicate with the server since no marshalling strategy has been configured on server side at org.jboss.ejb.client.remoting.VersionReceiver.handleMessage(VersionReceiver.java:96) at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456) at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Feb 17, 2017 10:44:50 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate INFO: EJBCLIENT000014: Version handshake not completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@3159c4b8, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@73846619,channel=jboss.ejb,nodename=tigris]}. Closing receiver context Exception in thread "Remoting "config-based-ejb-client-endpoint" task-8" java.lang.RuntimeException: Client cannot communicate with the server since no marshalling strategy has been configured on server side at org.jboss.ejb.client.remoting.VersionReceiver.handleMessage(VersionReceiver.java:96) at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:383) at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Feb 17, 2017 10:44:55 AM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate INFO: EJBCLIENT000014: Version handshake not completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@3159c4b8, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@73846619,channel=jboss.ejb,nodename=tigris]}. Closing receiver context Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-asynchronous-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@5abca1e0 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) at com.sun.proxy.$Proxy0.fireAndForget(Unknown Source) at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.fireAndForget(AsynchronousClient.java:76) at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.main(AsynchronousClient.java:158)
- is related to
-
JBEAP-9248 EJB client from EAP 7.0 can't invoke EJBs on EAP 7.1
-
- Closed
-