[JBoss JIRA] (WFLY-12865) .CLI command to write attribute is giving a StackOverflow Exception
by Jonathan Vila Lopez (Jira)
[ https://issues.redhat.com/browse/WFLY-12865?page=com.atlassian.jira.plugi... ]
Jonathan Vila Lopez commented on WFLY-12865:
--------------------------------------------
WORKAROUND / FIX :
With the help of [~yersan]and [~jamezp] it finally worked following these steps :
1. Add *reload* at the end of each command cli script
{code}
/subsystem=undertow/configuration=handler/file=windup-web-redirect:add(path=${jboss.home.dir}/windup-web-redirect)
/subsystem=undertow/server=default-server/host=default-host/location=\//:write-attribute(name=handler,value=windup-web-redirect)
command-timeout set 15000
reload
{code}
2. Add fork=true to the wildfly-maven-plugin
3. Add serverArgs=--admin-only to the wildfly-maven-plugin
4. Use latest (20191212) version of wildfly-maven-plugin : 2.0.2.Final
{code}
<execution>
<id>start-wildfly</id>
<phase>compile</phase>
<goals>
<goal>start</goal>
<goal>execute-commands</goal>
</goals>
<configuration>
<fork>true</fork>
<jbossHome>${project.build.directory}/${wildfly.directory}</jbossHome>
<serverConfig>standalone-full.xml</serverConfig>
<stdout>${project.build.directory}/jboss.stdout</stdout>
<systemProperties>
<windup.data.dir>${jboss.server.data.dir}/h2/windup-web</windup.data.dir>
</systemProperties>
<serverArgs>
<serverArg>--admin-only</serverArg>
</serverArgs>
<scripts>
<script>${project.build.directory}/${wildfly.directory}/bin/adapter-install.cli</script>
<script>src/main/cli/setup-eap.cli</script>
<script>src/main/cli/adding-redirect.cli</script>
</scripts>
<startupTimeout>300</startupTimeout>
</configuration>
</execution>
{code}
> .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: Management, Web (Undertow)
> Affects Versions: 18.0.1.Final
> Reporter: Jonathan Vila Lopez
> Assignee: Yeray Borges
> Priority: Blocker
> Fix For: 19.0.0.Beta1
>
>
> 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*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ]
Darran Lofthouse resolved WFWIP-284.
------------------------------------
Resolution: Rejected
The "Obsoleted By" / "Updated By" specifications are only replacing or enhancing specific sections of the HTTP 1.1 RFC, I see nothing that replaces the definitions of the header format.
The RFC however that was used to justify the raising of this bug report is specifically about e-mail messages - this is clarified within the first sentence of the abstract.
> Clarify what is invalid header name
> -----------------------------------
>
> Key: WFWIP-284
> URL: https://issues.redhat.com/browse/WFWIP-284
> Project: WildFly WIP
> Issue Type: Task
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Header names should follow rules described here:
> https://tools.ietf.org/html/rfc5322#section-2.2
> However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed.
> I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either.
> Is this on purpose?
> If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.redhat.com/browse/WFCORE-4763?page=com.atlassian.jira.plug... ]
Yann Le Tallec edited comment on WFCORE-4763 at 12/12/19 5:28 AM:
------------------------------------------------------------------
Hi [~brian.stansberry], I suppose my confusion comes from the semantic difference between `<any-address/>` and `<any> list </any>`.
If applied, say, to the management interface, the former allows to connect to port 9990 from any address (as expected) whereas the latter will only accept connections from the first valid address in the list and will reject connections from other addresses.
If you believe that's by design I will close the issue.
was (Author: assylias):
Hi [~brian.stansberry], I suppose my confusion comes from the semantic difference between `<any-address/>` and `<any> ... </any>`.
If applied, say, to the management interface, the former allows to connect to port 9990 from any address (as expected) whereas the latter will only accept connections from the first valid address and will reject connections from other addresses.
If you believe that's by design I will close the issue.
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFCORE-4763
> URL: https://issues.redhat.com/browse/WFCORE-4763
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another (VALID) IP address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally.
> - if I use {{subnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.redhat.com/browse/WFCORE-4763?page=com.atlassian.jira.plug... ]
Yann Le Tallec commented on WFCORE-4763:
----------------------------------------
Hi Brian, I suppose my confusion comes from the semantic difference between `<any-address/>` and `<any> ... </any>`.
If applied, say, to the management interface, the former allows to connect to port 9990 from any address (as expected) whereas the latter will only accept connections from the first valid address and will reject connections from other addresses.
If you believe that's by design I will close the issue.
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFCORE-4763
> URL: https://issues.redhat.com/browse/WFCORE-4763
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another (VALID) IP address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally.
> - if I use {{subnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected
by Yann Le Tallec (Jira)
[ https://issues.redhat.com/browse/WFCORE-4763?page=com.atlassian.jira.plug... ]
Yann Le Tallec edited comment on WFCORE-4763 at 12/12/19 5:27 AM:
------------------------------------------------------------------
Hi [~brian.stansberry], I suppose my confusion comes from the semantic difference between `<any-address/>` and `<any> ... </any>`.
If applied, say, to the management interface, the former allows to connect to port 9990 from any address (as expected) whereas the latter will only accept connections from the first valid address and will reject connections from other addresses.
If you believe that's by design I will close the issue.
was (Author: assylias):
Hi Brian, I suppose my confusion comes from the semantic difference between `<any-address/>` and `<any> ... </any>`.
If applied, say, to the management interface, the former allows to connect to port 9990 from any address (as expected) whereas the latter will only accept connections from the first valid address and will reject connections from other addresses.
If you believe that's by design I will close the issue.
> interface "any" tag not working as expected
> -------------------------------------------
>
> Key: WFCORE-4763
> URL: https://issues.redhat.com/browse/WFCORE-4763
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Environment: Ubuntu 18.02
> Reporter: Yann Le Tallec
> Priority: Major
>
> The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below.
> This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> </any>
> </interface>
> </interfaces>
> {code}
> But if I add another (VALID) IP address inside the any tag, I can't connect any more:
> {code:xml}
> <interfaces>
> <interface name="management">
> <any>
> <inet-address value="127.0.0.1"/>
> <inet-address value="10.20.230.26"/>
> </any>
> </interface>
> </interfaces>
> {code}
> With the latter configuration, {{connect}} fails with the following error:
> {noformat}
> >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
> {noformat}
> Note: to easily reproduce the problem from the cli, starting from a fresh standalone install:
> {code:bash}
> connect
> /interface=management:undefine-attribute(name=inet-address)
> /interface=management:undefine-attribute(name=any)
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]})
> reload
> /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]})
> reload
> {code}
> Notes:
> - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally.
> - if I use {{subnet-match}} I get the same issue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4864) accumulate causes NullPointerException
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4864?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-4864.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/21dd91cf3ff703f1f4c85a3b0f6962e...
> accumulate causes NullPointerException
> --------------------------------------
>
> Key: DROOLS-4864
> URL: https://issues.redhat.com/browse/DROOLS-4864
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.30.0.Final
> Reporter: Vedran Prišćan
> Assignee: Mario Fusco
> Priority: Blocker
> Labels: NullPointerException, accumulate
>
> NullPointerException is thrown in AddRemoveRule::iterateLeftTuple when *removing* a rule that contains *accumulate* with *max* function and a *source pattern that matches no object*.
> {noformat}
> Caused by: java.lang.NullPointerException
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.iterateLeftTuple(AddRemoveRule.java:1040)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.iterateLeftTuple(AddRemoveRule.java:1047)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.iterateLeftTuple(AddRemoveRule.java:1053)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.iterateLeftTuple(AddRemoveRule.java:1053)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.visitChild(AddRemoveRule.java:969)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.lambda$processLeftTuples$1(AddRemoveRule.java:927)
> at deployment.my-full-bundle.ear//org.drools.core.common.DefaultFactHandle$SingleLinkedTuples.forEachLeftTuple(DefaultFactHandle.java:728)
> at deployment.my-full-bundle.ear//org.drools.core.common.DefaultFactHandle.forEachLeftTuple(DefaultFactHandle.java:924)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:922)
> at deployment.my-full-bundle.ear//org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:178)
> at deployment.my-full-bundle.ear//org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:191)
> at deployment.my-full-bundle.ear//org.drools.core.reteoo.ReteooBuilder.removeRules(ReteooBuilder.java:177)
> at deployment.my-full-bundle.ear//org.drools.core.impl.KnowledgeBaseImpl.removeObjectsGeneratedFromResource(KnowledgeBaseImpl.java:1735)
> at deployment.my-full-bundle.ear//org.drools.compiler.builder.impl.KnowledgeBuilderImpl.removeObjectsGeneratedFromResource(KnowledgeBuilderImpl.java:2151)
> at deployment.my-full-bundle.ear//org.drools.compiler.kie.builder.impl.KieBaseUpdater.removeResources(KieBaseUpdater.java:121)
> at deployment.my-full-bundle.ear//org.drools.compiler.kie.builder.impl.KieBaseUpdater.run(KieBaseUpdater.java:66)
> at deployment.my-full-bundle.ear//org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:745)
> at deployment.my-full-bundle.ear//org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:267)
> at deployment.my-full-bundle.ear//org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:237)
> at deployment.my-full-bundle.ear//org.drools.compiler.kie.builder.impl.KieContainerImpl.updateToVersion(KieContainerImpl.java:195)
> at deployment.my-full-bundle.ear.rules-comp-impl.jar//com.my.rules.RuleKnowledgeBase.removeRuleFromKnowledgeBase(RuleKnowledgeBase.java:481)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12877) Use descriptive error message for duplicate host/context deployments
by Katarina Hermanova (Jira)
[ https://issues.redhat.com/browse/WFLY-12877?page=com.atlassian.jira.plugi... ]
Katarina Hermanova moved WFCORE-4767 to WFLY-12877:
---------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-12877 (was: WFCORE-4767)
Component/s: Web (Undertow)
(was: Server)
> Use descriptive error message for duplicate host/context deployments
> --------------------------------------------------------------------
>
> Key: WFLY-12877
> URL: https://issues.redhat.com/browse/WFLY-12877
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Paul Ferraro
> Assignee: Katarina Hermanova
> Priority: Minor
>
> If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons.
> What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFCORE-4767) Use descriptive error message for duplicate host/context deployments
by Katarina Hermanova (Jira)
[ https://issues.redhat.com/browse/WFCORE-4767?page=com.atlassian.jira.plug... ]
Katarina Hermanova commented on WFCORE-4767:
--------------------------------------------
[~brian.stansberry] moving it back to WFLY. Thanks and sorry for messing up.
> Use descriptive error message for duplicate host/context deployments
> --------------------------------------------------------------------
>
> Key: WFCORE-4767
> URL: https://issues.redhat.com/browse/WFCORE-4767
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Reporter: Paul Ferraro
> Assignee: Katarina Hermanova
> Priority: Minor
>
> If a user attempts to deploy a web application to a host/context to which another application is deployed, this will fail for obvious reasons.
> What isn't obvious is the error message. Currently, users will see a DuplicateServiceException. Ideally, the error message should indicate that another application is deployed for the same host and context path.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFWIP-286) MP Fault Tolerance - Fault Tolerance is missing logging code when activated
by Miroslav Novak (Jira)
Miroslav Novak created WFWIP-286:
------------------------------------
Summary: MP Fault Tolerance - Fault Tolerance is missing logging code when activated
Key: WFWIP-286
URL: https://issues.redhat.com/browse/WFWIP-286
Project: WildFly WIP
Issue Type: Bug
Components: MP Fault Tolerance
Reporter: Miroslav Novak
Assignee: Radoslav Husar
If MP FT is activated by deployment then INFO log is missing logging code:
{code}
10:18:31,626 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated
{code}
Logging code should be added.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months