May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8505) Adding Undertow application-security-domain requires reload but the operation outcome doesn't mention it

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8505?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-8505. ---------------------------------- Resolution: Rejected Rejected for reasons specified in the JBEAP JIRA > Adding Undertow application-security-domain requires reload but the operation outcome doesn't mention it > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-8505 > URL: https://issues.jboss.org/browse/WFLY-8505 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Reporter: Josef Cacek > Assignee: Stuart Douglas > Priority: Critical > > Add operation for the {{application-security-domain}} configuration in Undertow doesn't report that reload is required, but without the reload the change doesn't take effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8702) rewrite handler produces invalid URLs when used with query part

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-8702: ------------------------------------ Summary: rewrite handler produces invalid URLs when used with query part Key: WFLY-8702 URL: https://issues.jboss.org/browse/WFLY-8702 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Environment: * Windows 10 * Wildfly 10.1.0 Final Reporter: Markus Stier Assignee: Stuart Douglas Context: a request of the form "http://home:8180/" should be rewritten to "http://home:8180/somepath?param=1234" Problem: The rewrite handler produces URLs which contain duplicated query parts and question marks. See excerpt from access log below. {code} [26/Apr/2017:09:26:09 +0200] home:8180 "GET /somepath?param=1234??param=1234 HTTP/1.1" 404 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8697) Address DeploymentUnitProcessor leaks in the codebase

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8697?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-8697: -------------------------------------- This is not possible without a major rework of the DUP process, that would come with a significant memory cost. For some deployment processors this is simple, they add something to the DeploymentUnit, so undeploy can simply remove it, however for most of them it is not nearly this simple as they mutate data structures rather than just adding something. This would mean they would need to 'undo' what that have done, which in general would require a lot more book keeping, as they essentially need to store the state pre modification, which has a significant runtime memory cost. This is why the deployment is restarted on a dependency change, because even though we could force undeploy to be the opposite of deploy it is both very error prone and comes with a big runtime memory cost. > Address DeploymentUnitProcessor leaks in the codebase > ----------------------------------------------------- > > Key: WFLY-8697 > URL: https://issues.jboss.org/browse/WFLY-8697 > Project: WildFly > Issue Type: Task > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > In order to get singleton deployments fully working, we need to address the numerous {{org.jboss.as.server.deployment.DeploymentUnitProcessor#undeploy}} implementation leaks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8701) Upgrade WildFly HTTP client to 1.0.0.CR3

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8701?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-10729 to WFLY-8701: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8701 (was: JBEAP-10729) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Fix Version/s: (was: 7.1.0.DR18) > Upgrade WildFly HTTP client to 1.0.0.CR3 > ---------------------------------------- > > Key: WFLY-8701 > URL: https://issues.jboss.org/browse/WFLY-8701 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1132) Unable to load passwords from wildfly-config.xml

by Stuart Douglas (JIRA)

Stuart Douglas created ELY-1132: ----------------------------------- Summary: Unable to load passwords from wildfly-config.xml Key: ELY-1132 URL: https://issues.jboss.org/browse/ELY-1132 Project: WildFly Elytron Issue Type: Bug Reporter: Stuart Douglas Assignee: Darran Lofthouse I see the following exception, adding use-service-loader-providers does not help Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "clear" at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseClearPassword$47(ElytronXmlParser.java:2009) ... 46 more Looks like this should just be hard coded to use the Elytron provider? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8700) Upgrade EJB client to 4.0.0.Beta26

by David Lloyd (JIRA)

David Lloyd created WFLY-8700: --------------------------------- Summary: Upgrade EJB client to 4.0.0.Beta26 Key: WFLY-8700 URL: https://issues.jboss.org/browse/WFLY-8700 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2764) Upgrade WildFly Client Config to 1.0.0.Beta4

by David Lloyd (JIRA)

David Lloyd created WFCORE-2764: ----------------------------------- Summary: Upgrade WildFly Client Config to 1.0.0.Beta4 Key: WFCORE-2764 URL: https://issues.jboss.org/browse/WFCORE-2764 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta18 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8699) Upgrade naming client to 1.0.0.Beta15

by David Lloyd (JIRA)

David Lloyd created WFLY-8699: --------------------------------- Summary: Upgrade naming client to 1.0.0.Beta15 Key: WFLY-8699 URL: https://issues.jboss.org/browse/WFLY-8699 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8698) Upgrade naming client to 1.0.0.Beta15

by David Lloyd (JIRA)

David Lloyd created WFLY-8698: --------------------------------- Summary: Upgrade naming client to 1.0.0.Beta15 Key: WFLY-8698 URL: https://issues.jboss.org/browse/WFLY-8698 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8502) Upgrade transaction client to 1.0.0.Beta21 from 1.0.0.Beta19

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8502?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-8502. ------------------------------- Fix Version/s: 11.0.0.Beta1 Resolution: Done > Upgrade transaction client to 1.0.0.Beta21 from 1.0.0.Beta19 > ------------------------------------------------------------ > > Key: WFLY-8502 > URL: https://issues.jboss.org/browse/WFLY-8502 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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