]
Peter Jonsson commented on WFCORE-4775:
---------------------------------------
Just out of pure curiosity... may I ask a question to You guys;
I found that the very same error occurs in EAP 7.3.0 . How does the "knowledge
transfer" work in the Wildfly--->EAP? It seems like this one fell between the
chairs...
This error is a showstopper for all of our (isMobile) deliveries and now I have to bring
our EAP customers to a halt before they upgrade to EAP 7.3 while all of our Wildfly
customers are happy since they can go WF19 since last week.
Some .CLI commands that has been working since WF9 fails on WF18
----------------------------------------------------------------
Key: WFCORE-4775
URL:
https://issues.redhat.com/browse/WFCORE-4775
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 11.0.0.Beta4
Reporter: Peter Jonsson
Assignee: Yeray Borges Santana
Priority: Critical
Fix For: 11.0.0.Beta5, 11.0.0.Final
Error message is
ERROR [org.jboss.as.cli.CommandContext] (CLI command) {
"outcome" => "failed",
"failure-description" => "java.lang.StackOverflowError:null"
}
And in the log
2019-10-21 19:14:44,377 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) WFLYCTL0403: Unexpected failure during execution of the
following operation(s): [{
"address" => [("subsystem" => "undertow")],
"operation" => "write-attribute",
"name" => "statistics-enabled",
"value" => true,
"operation-headers" => {
"caller-type" => "user",
"access-mechanism" => "NATIVE"
}
}]: java.lang.StackOverflowError
at
org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:418)
at
org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
at
org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426)
at
org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)