[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase
by Brian Stansberry (JIRA)
[ 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=WildFlyCore... 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)
9 years, 2 months
[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8148?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-8148:
-----------------------------------
Description:
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=WildFlyCore... 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.
was:
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=WildFlyCore... 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}
Server log ERROR which explains why the JNDI lookup fails:
{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}
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.
> 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=WildFlyCore... 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)
9 years, 2 months
[JBoss JIRA] (LOGMGR-146) Suppressed exception format is not correct
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-146?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-146:
---------------------------------
Fix Version/s: 2.0.5.Final
2.1.0.Beta1
> Suppressed exception format is not correct
> ------------------------------------------
>
> Key: LOGMGR-146
> URL: https://issues.jboss.org/browse/LOGMGR-146
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: James Perkins
> Fix For: 2.0.5.Final, 2.1.0.Beta1
>
>
> The suppressed exception format is not correct when multiple exceptions are suppressed. Too many causes are printed likely because the circular dependencies are not working correctly.
> {code:java|title=Example Reproducer}
> final RuntimeException r1 = new RuntimeException("Exception 1");
> final RuntimeException r2 = new RuntimeException("Exception 2", r1);
> final RuntimeException r3 = new RuntimeException("Exception 3", r2);
> final RuntimeException cause = new RuntimeException("This is the cause", r1);
> cause.addSuppressed(r2);
> cause.addSuppressed(r3);
> Logger.getLogger(Main.class).error("Log message", cause);
> {code}
> {code:title=Output from JBoss Log Manager}
> 13:03:53,684 ERROR [com.jamezp.test.Main] Log message: java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> {code}
> {code:title=Output from Throwable.printStackTrace()}
> java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 2]
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 1]
> {code}
> {code:title=Output from JUL}
> Jan 26, 2017 1:06:29 PM com.jamezp.test.Main main
> ERROR: Log message
> java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 2]
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (LOGMGR-146) Suppressed exception format is not correct
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-146?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-146:
---------------------------------
Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/102, https://github.com/jboss-logging/jboss-logmanager/pull/103 (was: https://github.com/jboss-logging/jboss-logmanager/pull/102)
> Suppressed exception format is not correct
> ------------------------------------------
>
> Key: LOGMGR-146
> URL: https://issues.jboss.org/browse/LOGMGR-146
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: James Perkins
>
> The suppressed exception format is not correct when multiple exceptions are suppressed. Too many causes are printed likely because the circular dependencies are not working correctly.
> {code:java|title=Example Reproducer}
> final RuntimeException r1 = new RuntimeException("Exception 1");
> final RuntimeException r2 = new RuntimeException("Exception 2", r1);
> final RuntimeException r3 = new RuntimeException("Exception 3", r2);
> final RuntimeException cause = new RuntimeException("This is the cause", r1);
> cause.addSuppressed(r2);
> cause.addSuppressed(r3);
> Logger.getLogger(Main.class).error("Log message", cause);
> {code}
> {code:title=Output from JBoss Log Manager}
> 13:03:53,684 ERROR [com.jamezp.test.Main] Log message: java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> {code}
> {code:title=Output from Throwable.printStackTrace()}
> java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 2]
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 1]
> {code}
> {code:title=Output from JUL}
> Jan 26, 2017 1:06:29 PM com.jamezp.test.Main main
> ERROR: Log message
> java.lang.RuntimeException: This is the cause
> at com.jamezp.test.Main.main(Main.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Suppressed: java.lang.RuntimeException: Exception 2
> at com.jamezp.test.Main.main(Main.java:162)
> ... 5 more
> Caused by: java.lang.RuntimeException: Exception 1
> at com.jamezp.test.Main.main(Main.java:161)
> ... 5 more
> Suppressed: java.lang.RuntimeException: Exception 3
> at com.jamezp.test.Main.main(Main.java:163)
> ... 5 more
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 2]
> [CIRCULAR REFERENCE:java.lang.RuntimeException: Exception 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8148) Intermittent failure in InterDeploymentDependenciesEarTestCase
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-8148:
--------------------------------------
Summary: 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=WildFlyCore... 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}
Server log ERROR which explains why the JNDI lookup fails:
{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}
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)
9 years, 2 months
[JBoss JIRA] (WFCORE-2258) 500 return for nonexistent user in legacy ldap security realm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2258?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-2258:
-------------------------------------
Fix Version/s: 3.0.0.Beta3
> 500 return for nonexistent user in legacy ldap security realm
> -------------------------------------------------------------
>
> Key: WFCORE-2258
> URL: https://issues.jboss.org/browse/WFCORE-2258
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: regression
> Fix For: 3.0.0.Beta3
>
>
> In case of securing management interface with ldap in security realm. When nonexistent user is provided, wildfly answers with {{500}} http status code. It is different behaviour compared to wildfly 10.1, which returns {{401}}. I think http status code {{401}} is proper in this situation, because it is client fault (e.g. typo in username) and can be repaired on client side.
> {code:title=server.log}
> 10:49:18,745 TRACE [org.wildfly.security] (management task-10) Handling MechanismInformationCallback
> 10:49:18,746 TRACE [org.wildfly.security] (management task-10) Handling AvailableRealmsCallback: realms = [ldap-realm]
> 10:49:18,746 TRACE [org.wildfly.security] (management task-10) Handling RealmCallback: selected = [ldap-realm]
> 10:49:18,746 TRACE [org.wildfly.security] (management task-10) Handling NameCallback: authenticationName = anil
> 10:49:18,746 TRACE [org.wildfly.security] (management task-10) Name assigning: [anil], pre-realm rewritten: [anil], realm name: [PLAIN], post realm rewritten: [anil], realm rewritten: [anil]
> 10:49:18,746 TRACE [org.jboss.as.domain.management.security] (management task-10) Non caching search for 'anil'
> 10:49:18,746 TRACE [org.jboss.as.domain.management.security] (management task-10) Performing single level search
> 10:49:18,746 TRACE [org.jboss.as.domain.management.security] (management task-10) Searching for user 'anil' using filter '(uid={0})'.
> 10:49:18,746 TRACE [org.jboss.as.domain.management.security] (management task-10) Connecting to LDAP with properties ({java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.provider.url=ldap://localhost.localdomain:10389, java.naming.security.principal=uid=admin,ou=system, java.naming.security.credentials=***, java.naming.referral=ignore})
> 10:49:18,749 WARN [org.apache.directory.server.core.api.interceptor.context.FilteringOperationContext] (pool-7-thread-1) Requested attribute dn does not exist in the schema, it will be ignored
> 10:49:18,750 TRACE [org.jboss.as.domain.management.security] (management task-10) User 'anil' not found in directory.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2257) Missing username in LDAP entry for legacy ldap realm returns 500 instead of 401
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2257?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-2257.
--------------------------------------
Fix Version/s: 3.0.0.Beta3
Resolution: Duplicate Issue
> Missing username in LDAP entry for legacy ldap realm returns 500 instead of 401
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2257
> URL: https://issues.jboss.org/browse/WFCORE-2257
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Beta3
>
>
> In case when legacy LDAP Realm uses {{username-load}} attribute and its value does not exist in LDAP entry then current implementation returns status code 500. This is different behaviour from WildFly 10 where status code 401 is returned.
> This issue can be related to WFCORE-2258 (500 return for nonexistent user in legacy ldap security realm).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months