-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.ER2
-
None
-
Regression, Blocks Testing
-
-
-
-
-
-
-
This has been recently resolved by
EJBCLIENT-250.
After looking up a remote bean, setting invocation timeout to any value, for example 10 seconds, and invoking the remote bean, EJB client logs "TimeoutException: No invocation response received in 10000 milliseconds" immediately.
Set the invocation timeout
EJBClient.setInvocationTimeout(helloBeanRemote, 10, TimeUnit.SECONDS);
Full stacktrace
2017-07-12 10:16:00,886 5051 DEBUG [org.jboss.ejb.client.invocation] (main:) Calling invoke(module = /server/HelloBean, strong affinity = Cluster "ejb", weak affinity = Cluster "ejb"): 2017-07-12 10:16:00,889 5054 TRACE [org.jboss.ejb.client.invocation] (main:) Calling executeDiscovery(locator = StatefulEJBLocator for "/server/HelloBean", view is interface ejb.HelloBeanRemote, affinity is Cluster "ejb", session ID is UUIDSessionID [337fc7e1-fbe8-41ea-bd9a-d0116584e762], weak affinity = Cluster "ejb") 2017-07-12 10:16:00,889 5054 TRACE [org.jboss.ejb.client.invocation] (main:) Performing cluster discovery(locator = StatefulEJBLocator for "/server/HelloBean", view is interface ejb.HelloBeanRemote, affinity is Cluster "ejb", session ID is UUIDSessionID [337fc7e1-fbe8-41ea-bd9a-d0116584e762], weak affinity = Cluster "ejb", filter spec = (&(cluster=ejb)) javax.ejb.EJBException: java.util.concurrent.TimeoutException: No invocation response received in 10000 milliseconds at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:208) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:111) at com.sun.proxy.$Proxy3.hello(Unknown Source) at org.jboss.as.standaloneejbclient.Main.promptEnterKey(Main.java:664) at org.jboss.as.standaloneejbclient.Main.doSingleLookupWildflyConfig(Main.java:92) at org.jboss.as.standaloneejbclient.Main.main(Main.java:48) Caused by: java.util.concurrent.TimeoutException: No invocation response received in 10000 milliseconds at org.jboss.ejb.client.EJBClientInvocationContext.lambda$awaitResponse$3(EJBClientInvocationContext.java:870) at org.jboss.ejb.client.EJBClientInvocationContext$ThrowableResult.getResult(EJBClientInvocationContext.java:1124) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:563) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:500) at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:565) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:500) at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:99) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:565) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:500) at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:86) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:565) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:500) at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:907) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:178) ... 5 more
- is caused by
-
EJBCLIENT-250 Invocation timeout not being processed correctly
- Resolved