May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2800) contrib systemd script uses systemd enable|start wildfly.service

by Filippe Spolti (JIRA)

Filippe Spolti created WFCORE-2800: -------------------------------------- Summary: contrib systemd script uses systemd enable|start wildfly.service Key: WFCORE-2800 URL: https://issues.jboss.org/browse/WFCORE-2800 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Filippe Spolti Assignee: Filippe Spolti The command used in the $WFLY_HOME/docs/contrib/scripts/systemd/README to enable and start the wildfly service is not correct. The correct one is systemctl. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8762) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8762?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-8762: --------------------------------- Assignee: Tomaz Cerar (was: Stuart Douglas) > WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references > --------------------------------------------------------------------------------------- > > Key: WFLY-8762 > URL: https://issues.jboss.org/browse/WFLY-8762 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > > This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-773) Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-773?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-773: ------------------------------------ Assignee: Darran Lofthouse (was: David Lloyd) > Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]> > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-773 > URL: https://issues.jboss.org/browse/ELY-773 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > This may be obsoleted by ongoing work but just wanted an issue to track where AuthenticationConfiguration and related classes currently uses PaswordFactory.getInstance without passing in a Supplier for Provider[]. > * SetCredentialsConfiguration > * SetKeyStoreCredentialAuthenticationConfiguration > * ElytronAuthenticator > * ElytronXmlParser. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-773) Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-773?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-773: --------------------------------- Fix Version/s: 1.1.0.Beta43 (was: 1.1.0.Beta44) > Where AuthenticationConfiguration has calls to PasswordFactory.getInstance(alg) pass in Supplier<Provider[]> > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-773 > URL: https://issues.jboss.org/browse/ELY-773 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > This may be obsoleted by ongoing work but just wanted an issue to track where AuthenticationConfiguration and related classes currently uses PaswordFactory.getInstance without passing in a Supplier for Provider[]. > * SetCredentialsConfiguration > * SetKeyStoreCredentialAuthenticationConfiguration > * ElytronAuthenticator > * ElytronXmlParser. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-837) Clean up provider usage and definition in XML config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-837?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-837: ------------------------------------ Assignee: Darran Lofthouse > Clean up provider usage and definition in XML config > ---------------------------------------------------- > > Key: ELY-837 > URL: https://issues.jboss.org/browse/ELY-837 > Project: WildFly Elytron > Issue Type: Task > Components: XML > Reporter: David Lloyd > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > We are very inconsistent about how we're defining and using providers in the XML configuration. We need to meet the following requirements: > * Provide a single top-level element from the substitution group {{abstract-providers}} that specifies the providers to use in the absence of any other configuration; default to {{use-system-providers}} > * Update the following types (or appropriate enclosing type) to accept an optional nested {{abstract-providers}} override: > ** {{key-store-type}} > ** {{credential-store-type}} > ** {{hashed-password-type}} > * Update the following types to use an optional {{provider}} *attribute* (not nested element) to allow selection of a specific provider: > ** {{credential-store-type}} > ** {{key-store-type}} -- already done! > ** {{hashed-password-type}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-837) Clean up provider usage and definition in XML config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-837?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-837: --------------------------------- Fix Version/s: 1.1.0.Beta43 > Clean up provider usage and definition in XML config > ---------------------------------------------------- > > Key: ELY-837 > URL: https://issues.jboss.org/browse/ELY-837 > Project: WildFly Elytron > Issue Type: Task > Components: XML > Reporter: David Lloyd > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > We are very inconsistent about how we're defining and using providers in the XML configuration. We need to meet the following requirements: > * Provide a single top-level element from the substitution group {{abstract-providers}} that specifies the providers to use in the absence of any other configuration; default to {{use-system-providers}} > * Update the following types (or appropriate enclosing type) to accept an optional nested {{abstract-providers}} override: > ** {{key-store-type}} > ** {{credential-store-type}} > ** {{hashed-password-type}} > * Update the following types to use an optional {{provider}} *attribute* (not nested element) to allow selection of a specific provider: > ** {{credential-store-type}} > ** {{key-store-type}} -- already done! > ** {{hashed-password-type}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8762) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-8762: -------------------------------------- Summary: WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references Key: WFLY-8762 URL: https://issues.jboss.org/browse/WFLY-8762 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Brian Stansberry Assignee: Stuart Douglas This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2782) Executing CLI file fails with encoding ANSI (Windows-1252)

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2782?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFCORE-2782: --------------------------------- Summary: Executing CLI file fails with encoding ANSI (Windows-1252) (was: [GSS](7.1.0) Executing CLI file fails with encoding ANSI (Windows-1252)) > Executing CLI file fails with encoding ANSI (Windows-1252) > ---------------------------------------------------------- > > Key: WFCORE-2782 > URL: https://issues.jboss.org/browse/WFCORE-2782 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Executing the CLI with file encoding ANSI (Windows-1252) where characters include German umlauts (ä, ö, ü) fails. > This worked in EAP 7.0.0, but fails in 7.1.0 Alpha. Also present in DR17 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2782) [GSS](7.1.0) Executing CLI file fails with encoding ANSI (Windows-1252)

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2782?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFCORE-2782: --------------------------------- Summary: [GSS](7.1.0) Executing CLI file fails with encoding ANSI (Windows-1252) (was: Executing CLI file fails with encoding ANSI (Windows-1252)) > [GSS](7.1.0) Executing CLI file fails with encoding ANSI (Windows-1252) > ----------------------------------------------------------------------- > > Key: WFCORE-2782 > URL: https://issues.jboss.org/browse/WFCORE-2782 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Executing the CLI with file encoding ANSI (Windows-1252) where characters include German umlauts (ä, ö, ü) fails. > This worked in EAP 7.0.0, but fails in 7.1.0 Alpha. Also present in DR17 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-20) Misc. code improvements suggested by static analysis

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-20?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-20. ----------------------------- Resolution: Done > Misc. code improvements suggested by static analysis > ----------------------------------------------------- > > Key: AG-20 > URL: https://issues.jboss.org/browse/AG-20 > Project: Agroal > Issue Type: Task > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 May 2017