December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-12945) Migrate undertow subsystem to new MSC value API

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12945?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12945: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Migrate undertow subsystem to new MSC value API > ----------------------------------------------- > > Key: WFLY-12945 > URL: https://issues.redhat.com/browse/WFLY-12945 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 23.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13519) Infinispan module attribute needs to support multiple values

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13519?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13519: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Infinispan module attribute needs to support multiple values > ------------------------------------------------------------ > > Key: WFLY-13519 > URL: https://issues.redhat.com/browse/WFLY-13519 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 23.0.0.Beta1 > > > The cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. > Additionally, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). > Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. Users wanting to a specific Infinispan module has a similar issue. > Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. > In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. > Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12881: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Cannot customize split behavior and merge policy for Infinispan partition handling > ---------------------------------------------------------------------------------- > > Key: WFLY-12881 > URL: https://issues.redhat.com/browse/WFLY-12881 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final, 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 23.0.0.Beta1 > > > Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs. > Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13679) Make legacy security optional for "org.wildfly.iiop-openjdk"

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13679?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13679: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Make legacy security optional for "org.wildfly.iiop-openjdk" > ------------------------------------------------------------ > > Key: WFLY-13679 > URL: https://issues.redhat.com/browse/WFLY-13679 > Project: WildFly > Issue Type: Task > Components: IIOP, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 23.0.0.Beta1 > > > The dependency needs to optional so provisioning a layer with iiop-openjdk does not automatically pull in legacy security. > This is not just about making the module dependency optional, this is about understanding why it is not optional and identifying the steps required to make it optional. > This needs to consider: > * Default Configuration > * User Defined Configuration > Both of these can have different consequences depending on of they are used for: > * Resource defined services > * DeploymentUnitProcessor processing > iiop-openjdk module.xml: https://github.com/wildfly/wildfly/blob/master/ee-feature-pack/common/src... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13802) The undertow layer can not deploy deployments without the ee layer

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13802?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13802: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > The undertow layer can not deploy deployments without the ee layer > ------------------------------------------------------------------ > > Key: WFLY-13802 > URL: https://issues.redhat.com/browse/WFLY-13802 > Project: WildFly > Issue Type: Bug > Components: Build System, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 23.0.0.Beta1 > > > {code:java} > 16:35:06,234 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) > 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:1990) > 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.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50) > at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:709) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:276) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13883) Clustering TS: Enable Infinispan Server integration tests on Windows platform

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13883?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13883: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Clustering TS: Enable Infinispan Server integration tests on Windows platform > ----------------------------------------------------------------------------- > > Key: WFLY-13883 > URL: https://issues.redhat.com/browse/WFLY-13883 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 23.0.0.Beta1 > > > Currently disabled due to ISPN-12041. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14027) Restructure the application-client quickstart

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14027?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14027: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Restructure the application-client quickstart > --------------------------------------------- > > Key: WFLY-14027 > URL: https://issues.redhat.com/browse/WFLY-14027 > Project: WildFly > Issue Type: Task > Components: Application Client, Quickstarts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 23.0.0.Beta1 > > > At the moment the EJB is being deployed to the server but it is also in the ear used to invoke appclient.xml so gets deployed on the client as well. > As the intent of this quickstart is to illustrate an appclient invoking an EJB on a separate process I think it would be clearer if the server side process only contained the EJB and the client side process only contained the client itself plus any dependencies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14236) HotRodSessionManager expiration listener thread applies unnecessary JNDI context

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14236: ----------------------------------- Summary: HotRodSessionManager expiration listener thread applies unnecessary JNDI context Key: WFLY-14236 URL: https://issues.redhat.com/browse/WFLY-14236 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 22.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Threads currently use the default set of clustering contexts, including jndi context. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13858) Bump the Undertow subsystem model version and schema to version 12

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13858?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13858: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Bump the Undertow subsystem model version and schema to version 12 > ------------------------------------------------------------------ > > Key: WFLY-13858 > URL: https://issues.redhat.com/browse/WFLY-13858 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Affects Versions: 20.0.1.Final > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 23.0.0.Beta1 > > > The Undertow subsystem schema should be bumped from 9 to 10 and the model version should be bumped from 9 to 10. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14019) Add the Elytron subsystem and initial configuration to appclient.xml

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14019?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14019: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Beta1) > Add the Elytron subsystem and initial configuration to appclient.xml > -------------------------------------------------------------------- > > Key: WFLY-14019 > URL: https://issues.redhat.com/browse/WFLY-14019 > Project: WildFly > Issue Type: Sub-task > Components: Application Client, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Labels: EE9 > Fix For: 23.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020