[
https://issues.jboss.org/browse/WFLY-8148?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-8148:
----------------------------------------
My original post of this JIRA's description said the following was the cause of
failure but that is incorrect:
{code}
[0m[31m10:41:54,799 ERROR
[org.jboss.as.controller.management-operation] (management-handler-thread - 1)
WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment"
=> "app2.ear")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.deployment.unit.\"app1.ear\".deploymentCompleteService"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\"app2.ear\".\"hello.jar\".PARSE is
missing [jboss.deployment.unit.\"app1.ear\".deploymentCompleteService]",
"jboss.deployment.unit.\"app2.ear\".PARSE is missing
[jboss.deployment.unit.\"app1.ear\".deploymentCompleteService]"
]
}
[0m[31m10:41:54,799 ERROR [org.jboss.as.server]
(management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "app2.ear" was
rolled back with the following failure message:
{
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.deployment.unit.\"app1.ear\".deploymentCompleteService"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\"app2.ear\".\"hello.jar\".PARSE is
missing [jboss.deployment.unit.\"app1.ear\".deploymentCompleteService]",
"jboss.deployment.unit.\"app2.ear\".PARSE is missing
[jboss.deployment.unit.\"app1.ear\".deploymentCompleteService]"
]
}
{code}
That logging is expected and correct. The test deliberately deploys and app2.ear that
depends on app1.ear, but before app1.ear is deployed. So that is expected to fail and ^^^
is just the logging associated with that failure.
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)