November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12821) Request that only removes attributes from a distributed web session fails to replicate removals

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12821: ----------------------------------- Summary: Request that only removes attributes from a distributed web session fails to replicate removals Key: WFLY-12821 URL: https://issues.jboss.org/browse/WFLY-12821 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro This only affect coarse granularity sessions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4801) Remove unused conf var form HACEP

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4801: ------------------------------------------ Summary: Remove unused conf var form HACEP Key: DROOLS-4801 URL: https://issues.jboss.org/browse/DROOLS-4801 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12820) Request that only removes attributes from a distributed web session fails to replicate removals

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12820: ----------------------------------- Summary: Request that only removes attributes from a distributed web session fails to replicate removals Key: WFLY-12820 URL: https://issues.jboss.org/browse/WFLY-12820 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro This only affect coarse granularity sessions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-275) If MP FT microservice is undeployed then new MP FT microservice must use old Hystrix instance

by Miroslav Novak (Jira)

Miroslav Novak created WFWIP-275: ------------------------------------ Summary: If MP FT microservice is undeployed then new MP FT microservice must use old Hystrix instance Key: WFWIP-275 URL: https://issues.jboss.org/browse/WFWIP-275 Project: WildFly WIP Issue Type: Bug Reporter: Miroslav Novak Assignee: Radoslav Husar In case that MP FT deployment configures Hystrix in some then after its undeployment and chaning configuration for Hystrix, this configuration must be applied (Hystrix restarted). Test scenario: * Deploy MP FT microservice * Undeploy and deploy another one with different configuration for Hystrix Expected result: Check that new configuration for hystrix is applied (hystrix restarted with new configuration) Actaul result: New configuration for Hystrix is not applied -- 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 Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFWIP-272?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFWIP-272. ------------------------------------ Resolution: Done https://github.com/darranl/wildfly-core/commit/e6f8defd9ceec6ff7f0ae46d87... > 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] (WFCORE-4391) Upgrade apacheds-all to 2.0.0-M24 for Elytron tests

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4391?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4391: -------------------------------- Fix Version/s: 11.0.0.Beta4 (was: 11.0.0.Beta3) > Upgrade apacheds-all to 2.0.0-M24 for Elytron tests > --------------------------------------------------- > > Key: WFCORE-4391 > URL: https://issues.jboss.org/browse/WFCORE-4391 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 11.0.0.Beta4 > > > This upgrade is needed to avoid a race condition in Apache Directory Server that causes a hang in {{org.wildfly.extension.elytron.LdapTestCase}} with TLS 1.3. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-3376?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3376: -------------------------------- Fix Version/s: 11.0.0.Beta4 (was: 11.0.0.Beta3) > Modules may create loggers on a deployments log context > ------------------------------------------------------- > > Key: WFCORE-3376 > URL: https://issues.jboss.org/browse/WFCORE-3376 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 11.0.0.Beta4 > > > Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader. > What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1110) Allow addition of HTTP headers to management console responses

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-1110?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-1110: -------------------------------- Fix Version/s: 11.0.0.Beta4 (was: 11.0.0.Beta3) > Allow addition of HTTP headers to management console responses > -------------------------------------------------------------- > > Key: WFCORE-1110 > URL: https://issues.jboss.org/browse/WFCORE-1110 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: James Livingston > Assignee: Darran Lofthouse > Priority: Major > Labels: eap > Fix For: 11.0.0.Beta4 > > > It would be useful to be able to add additional HTTP headers to the responses from the web management console, such as X-Frame-Options. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-944?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFCORE-944: ------------------------------- Fix Version/s: 11.0.0.Beta4 (was: 11.0.0.Beta3) > truststore path is ignored if provider is not JKS > ------------------------------------------------- > > Key: WFCORE-944 > URL: https://issues.jboss.org/browse/WFCORE-944 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Arto Huusko > Priority: Major > Fix For: 11.0.0.Beta4 > > > truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS. > This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working. > We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured. > Even standard java supports PKCS12 truststores, where the same problem would occur. > So I would suggest that > - if provider is JKS, path is mandatory > - if provider is not JKS, but path is specified, it is passed to the provider -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4486) Support for multiple security realms - Failover

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4486?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4486: -------------------------------- Fix Version/s: 11.0.0.Beta4 (was: 11.0.0.Beta3) > Support for multiple security realms - Failover > ----------------------------------------------- > > Key: WFCORE-4486 > URL: https://issues.jboss.org/browse/WFCORE-4486 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Martin Mazanek > Priority: Major > Labels: CD17-Deferred, EAP-CD19 > Fix For: 11.0.0.Beta4 > > > Our security realms are able to indicate unavailability by throwing a RealmUnavailableException > We should support fail over to an alternative realm. > A common request is fail over to a local file based realm if an LDAP or database server has gone down allowing administrators to retain access to the server. -- 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