Description of problem:
Overlay tests, such as org.jboss.as.test.integration.deployment.deploymentoverlay.ear.OverlayExistingResourceTestCase or org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayNonExistingResourceTestCase fail from time to time with exception like this:
java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:overlayed, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@169076
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:747)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)
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.$Proxy51.fetchResource(Unknown Source)
Overlay tests seem to do lots of deploy/undeploy operations, which result in DeploymentRepository.add, DeploymentRepository.startDeployment and DeploymentRepository.remove calls. Exception like this might occur when remove call from the previous undeploy operation is being executed after add call of the following deploy operation.
How reproducible/Steps to Reproduce:
Can be reproduced locally by setting breakpoints in DeploymentRepository methods, executing ./integration-tests.sh clean install -Dtest=org.jboss.as.test.integration.deployment.deploymentoverlay.*.*TestCase.java -Dintegration.module -Dts.basic -DtestLogToFile -Ddebug
and releasing execution shortly after it hits breakpoint, but unreliably. Also exceptions could be noticed in CI environment, supposedly when it is under the load. First noticed in https://github.com/jbossas/jboss-eap/pull/2878 test results, but PR itself does not seem to be the cause.
Actual results: no test failures
Expected results: failure around OverlayUtils.setupOverlay call or similar
Additional info:
UPD: surely,
Expected results: no test failures
Actual results: failure around OverlayUtils.setupOverlay call or similar
Comment 2Enrique Gonzalez Martinez
2016-11-23 12:06:28 UTC
this looks like a race condition when the deployment happens before the ejb client tries to access the app... the tests need to ensure that deployment has been performed.
I'm not sure if there is a reliable way to know when a deployment has been performed. I guess something like ServerReload class should be tried here to fix a problem like this (not sure if it is backported in 6.4.x branch)
Comment 3Enrique Gonzalez Martinez
2016-11-23 12:07:25 UTC
rectify my last comment.... it is the other way round... the ejb client tries to connect before the deployment
Enrique,
yes, I can imagine this being the cause. Remote client calls previously waited until deployment becomes available, but later the behaviour was changed to make them fail fast. If there is no happens-before relationship between deployment being done and client sending requests, the result might look like this.
Description of problem: Overlay tests, such as org.jboss.as.test.integration.deployment.deploymentoverlay.ear.OverlayExistingResourceTestCase or org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayNonExistingResourceTestCase fail from time to time with exception like this: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:overlayed, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@169076 at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:747) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) 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.$Proxy51.fetchResource(Unknown Source) Overlay tests seem to do lots of deploy/undeploy operations, which result in DeploymentRepository.add, DeploymentRepository.startDeployment and DeploymentRepository.remove calls. Exception like this might occur when remove call from the previous undeploy operation is being executed after add call of the following deploy operation. How reproducible/Steps to Reproduce: Can be reproduced locally by setting breakpoints in DeploymentRepository methods, executing ./integration-tests.sh clean install -Dtest=org.jboss.as.test.integration.deployment.deploymentoverlay.*.*TestCase.java -Dintegration.module -Dts.basic -DtestLogToFile -Ddebug and releasing execution shortly after it hits breakpoint, but unreliably. Also exceptions could be noticed in CI environment, supposedly when it is under the load. First noticed in https://github.com/jbossas/jboss-eap/pull/2878 test results, but PR itself does not seem to be the cause. Actual results: no test failures Expected results: failure around OverlayUtils.setupOverlay call or similar Additional info: