-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Both DatabaseTimerServiceMultiNodeExecutionDisabledTestCase and DatabaseTimerServiceMultiNodeTestCase rely on specifying the jboss.naming.client.ejb.context property during InitialContext creation in order to ensure that an EJBClientContext will get set up properly with an appropriate EJBReceiver. Since the new WildFly naming client doesn't currently handle this property, we need to manually set the EJBClientConfiguration in this test for now. We need to revisit this modification when the new WildFly naming client and EJB client are being integrated. Note that without this modification, the tests fail with the following error:
java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:testTimerServiceSimple, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@6548bb7d at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:774) 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.$Proxy24.scheduleTimer(Unknown Source) at org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase.testEjbTimeoutOnOtherNode(DatabaseTimerServiceMultiNodeExecutionDisabledTestCase.java:197)
- is cloned by
-
-
- Closed
-
