November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4753) Upgrade JBoss Modules from 1.9.1.Final to 1.9.2.Final

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4753: ------------------------------------ Summary: Upgrade JBoss Modules from 1.9.1.Final to 1.9.2.Final Key: WFCORE-4753 URL: https://issues.jboss.org/browse/WFCORE-4753 Project: WildFly Core Issue Type: Component Upgrade Components: Build System, Modules Reporter: Yeray Borges Assignee: Yeray Borges -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4785) DRL applies even if groupflow was not assigned 7.5

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4785: ------------------------------------ Summary: DRL applies even if groupflow was not assigned 7.5 Key: DROOLS-4785 URL: https://issues.jboss.org/browse/DROOLS-4785 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Affects Versions: 7.5.0.Final Reporter: Anna Dupliak Assignee: Daniele Zonca *For version 7.5* # Given Traffic repo # Edit DRL driver status rules {code}rule "Status 1: young driver" when driver: Driver(age <= 18) then driver.setStatus("young"); end rule "Status 2: young adult driver" when driver: Driver(age > 18 && < 25) then driver.setStatus("young adult"); end rule "Status 3: adult driver" when driver: Driver(age >= 25) then driver.setStatus("adult"); end {code} # Go to Driver Status Rules Tests.scesim # Run the Tests Expected : Tests failed bcs the values null expected (no DRL rules are applied) Actual: Tests passed rules group was not updated -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4785) DRL applies even if groupflow was not assigned 7.5

by Anna Dupliak (Jira)

[ https://issues.jboss.org/browse/DROOLS-4785?page=com.atlassian.jira.plugi... ] Anna Dupliak updated DROOLS-4785: --------------------------------- Issue Type: Bug (was: Enhancement) > DRL applies even if groupflow was not assigned 7.5 > -------------------------------------------------- > > Key: DROOLS-4785 > URL: https://issues.jboss.org/browse/DROOLS-4785 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.5.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > > *For version 7.5* > # Given Traffic repo > # Edit DRL driver status rules > {code}rule "Status 1: young driver" > when > driver: Driver(age <= 18) > then > driver.setStatus("young"); > end > rule "Status 2: young adult driver" > when > driver: Driver(age > 18 && < 25) > then > driver.setStatus("young adult"); > end > rule "Status 3: adult driver" > when > driver: Driver(age >= 25) > then > driver.setStatus("adult"); > end {code} > # Go to Driver Status Rules Tests.scesim > # Run the Tests > Expected : Tests failed bcs the values null expected (no DRL rules are applied) > Actual: Tests passed rules group was not updated -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-269: ------------------------------ Component/s: Security > Colon in a header name doesn't show a warning > --------------------------------------------- > > Key: WFWIP-269 > URL: https://issues.jboss.org/browse/WFWIP-269 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Execute: > {code:java} > /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) > {code} > Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but users should at least see a warning describing this behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-268) Specifying empty list of constant-headers causes fatal error

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-268?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-268: ------------------------------ Component/s: Security > Specifying empty list of constant-headers causes fatal error > ------------------------------------------------------------ > > Key: WFWIP-268 > URL: https://issues.jboss.org/browse/WFWIP-268 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Specifying empty list of constant-headers causes fatal error. > {code:java} > 17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: "WFLYCTL0155: 'headers' may not be null" > 17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-270) Configured headers can override headers added by the corresponding endpoint

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-270?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-270: ------------------------------ Component/s: Security > Configured headers can override headers added by the corresponding endpoint > --------------------------------------------------------------------------- > > Key: WFWIP-270 > URL: https://issues.jboss.org/browse/WFWIP-270 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > [Analysis document|https://github.com/wildfly/wildfly-proposals/pull/263] says that > 'Configured headers will not override any headers added by the corresponding endpoint.' > However, I was able to override Connection and Date headers on /management endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-271) Header name must not contain space

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-271?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-271: ------------------------------ Component/s: Security > Header name must not contain space > ---------------------------------- > > Key: WFWIP-271 > URL: https://issues.jboss.org/browse/WFWIP-271 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Constant-headers allows to configure header name containing space, which shouldn't be possible according to > https://tools.ietf.org/html/rfc5322#section-2.2 > A field name MUST be composed of printable US-ASCII characters (i.e.,characters that have values between 33 and 126, inclusive), except colon. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-272) Specifying header name containing '\'n in constant-headers causes fatal error

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-272?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-272: ------------------------------ Component/s: Security > Specifying header name containing '\'n in constant-headers causes fatal error > ----------------------------------------------------------------------------- > > Key: WFWIP-272 > URL: https://issues.jboss.org/browse/WFWIP-272 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Specifying header name containing '\'n in constant-headers causes fatal error: > {code:java} > 10:02:36,853 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: WFLYSRV0083: Failed to start the http-interface service > at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:393) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A > B > at io.undertow.util.HttpString.checkForNewlines(HttpString.java:126) > at io.undertow.util.HttpString.<init>(HttpString.java:120) > at io.undertow.util.HttpString.<init>(HttpString.java:103) > at org.jboss.as.domain.http.server.StaticHeadersHandler$HeaderConstant.<init>(StaticHeadersHandler.java:70) > at org.jboss.as.domain.http.server.StaticHeadersHandler.addHeader(StaticHeadersHandler.java:61) > at org.jboss.as.domain.http.server.ManagementHttpServer.setupOpenListener(ManagementHttpServer.java:369) > at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:279) > at org.jboss.as.domain.http.server.ManagementHttpServer.access$2600(ManagementHttpServer.java:111) > at org.jboss.as.domain.http.server.ManagementHttpServer$Builder.build(ManagementHttpServer.java:666) > at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:351) > ... 8 more > 10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service > Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A > B"}} > 10:02:36,856 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.management.http.extensible" => "WFLYSRV0083: Failed to start the http-interface service > Caused by: java.lang.IllegalArgumentException: UT000149: HttpString is not allowed to contain newlines. value: A > B"}} > 10:02:36,868 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 10:02:36,875 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 3ms > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-271) Header name must not contain space

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-271?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-271: ------------------------------ Steps to Reproduce: Execute the following cli commands: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A B, value=abc}]}]) {code} {code:java} reload {code} See response headers: {code:java} curl -v http://localhost:9990/management {code} {code:java} A B: abc {code} was: Execute the following cli command: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A B, value=abc}]}]) {code} See response headers: {code:java} curl -v http://localhost:9990/management {code} {code:java} A B: abc {code} > Header name must not contain space > ---------------------------------- > > Key: WFWIP-271 > URL: https://issues.jboss.org/browse/WFWIP-271 > Project: WildFly WIP > Issue Type: Bug > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Constant-headers allows to configure header name containing space, which shouldn't be possible according to > https://tools.ietf.org/html/rfc5322#section-2.2 > A field name MUST be composed of printable US-ASCII characters (i.e.,characters that have values between 33 and 126, inclusive), except colon. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-269: ------------------------------ Steps to Reproduce: Execute the following commands: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} {code:java} reload {code} was: Execute the following command: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} > Colon in a header name doesn't show a warning > --------------------------------------------- > > Key: WFWIP-269 > URL: https://issues.jboss.org/browse/WFWIP-269 > Project: WildFly WIP > Issue Type: Bug > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Execute: > {code:java} > /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) > {code} > Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but users should at least see a warning describing this behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2019