]
Brian Stansberry updated WFLY-8148:
-----------------------------------
Comment: was deleted
(was: Never mind the previous comment; it still fails intermittently, although the
WFLY-8149 fix does prevent the failure resulting in 200 other tests failing.)
Intermittent failure in InterDeploymentDependenciesEarTestCase
--------------------------------------------------------------
Key: WFLY-8148
URL:
https://issues.jboss.org/browse/WFLY-8148
Project: WildFly
Issue Type: Bug
Components: EE, Test Suite
Reporter: Brian Stansberry
On a fairly frequent basis we are seeing failures in
InterDeploymentDependenciesEarTestCase. This then seems to be followed by ~ 200 other
failures.
https://ci.wildfly.org/viewLog.html?buildId=46213&buildTypeId=WildFly...
is an example.
Pattern is:
Failure:
{code}
javax.ejb.NoSuchEJBException: No such EJB: app2/hello/LogAccessBean
at
org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:354)
at
org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:75)
at
org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:357)
at
org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:608)
at
org.jboss.ejb.client.EJBInvocationHandler.lambda$invoke$0(EJBInvocationHandler.java:164)
at
org.jboss.ejb.client.EJBClientContext.discoverAffinityNone(EJBClientContext.java:428)
at
org.jboss.ejb.client.EJBClientContext.performLocatedAction(EJBClientContext.java:387)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:150)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100)
at com.sun.proxy.$Proxy65.getLog(Unknown Source)
at
org.jboss.as.test.integration.deployment.dependencies.ear.InterDeploymentDependenciesEarTestCase.test(InterDeploymentDependenciesEarTestCase.java:127)
{code}
Earliest failure I see with this pattern in the TeamCity history is from Aug 17, 2016.
But such failures were confined to JDK9 runs and stopped last Sept 2. Then they start
appearing quite frequently on Feb 6, 2017. First appearance was in a test of PR #9600, but
there are other failures before that PR was merged so I doubt that PR is relevant.