]
Jonathan Vila Lopez updated WFLY-12865:
---------------------------------------
Summary: .CLI command to write attribute is giving a StackOverflow Exception (was:
.CLI command to write attribute is givin an StackOverflow Exception)
.CLI command to write attribute is giving a StackOverflow Exception
-------------------------------------------------------------------
Key: WFLY-12865
URL:
https://issues.redhat.com/browse/WFLY-12865
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 18.0.1.Final
Reporter: Jonathan Vila Lopez
Assignee: Flavia Rainone
Priority: Blocker
In the RHAMT team we are trying to migrate the application from WF 15 to WF 18.
As part of the build the process starts WF and execute few .cli commands .
I get a StackOverflowError in a command :
{code:java}
/subsystem=undertow/server=default-server/host=default-host/location=\//:write-attribute(name=handler,value=windup-web-redirect)
Error
Command execution failed for command
'/subsystem=undertow/server=default-server/host=default-host/location=\//:write-attribute(name=handler,value=windup-web-redirect)'.
{
[ERROR] "outcome" => "failed",
[ERROR] "failure-description" =>
"java.lang.StackOverflowError:null"
[ERROR] }
^[[0m^[[31m17:48:42,651 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 1) WFLYCTL0403: Unexpected failure during execution of the
following operation(s): [{
"address" => [
("subsystem" => "undertow"),
("server" => "default-server"),
("host" => "default-host"),
("location" => "/")
],
"operation" => "write-attribute",
"name" => "handler",
"value" => "windup-web-redirect",
"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)
at
org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426)
at
org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392)
at
org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426)
{code}
If I connect to WF 18, using jboss-cli.sh and this is the result of the read command :
{code}
[standalone@localhost:9990 /]
/subsystem=undertow/server=default-server/host=default-host/location=\//:read-attribute(name=handler)
{
"outcome" => "success",
"result" => "welcome-content",
"response-headers" => {"process-state" =>
"restart-required"}
}
{code}
But if I do the write command :
{code}
[standalone@localhost:9990 /]
/subsystem=undertow/server=default-server/host=default-host/location=\//:write-attribute(name=handler,value=windup-web-redirect)
{
"outcome" => "failed",
"failure-description" => "java.lang.StackOverflowError:null"
}
{code}
Even if I try to write the same value as I get from the read command it gives the same
error.
If I try to use *add* instead of *write-attribute*, I get a resource duplicated error.
*This is stopping our current migration of RHAMT 4.3.0 to WF 18*