July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3040) StepCapabilityStatus should take dynamic capability dependencies into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3040?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3040: ------------------------------------------ [~ehugonnet] WFLY-9116 is fixed so you shouldn't be seeing this problem any more. > StepCapabilityStatus should take dynamic capability dependencies into account > ----------------------------------------------------------------------------- > > Key: WFCORE-3040 > URL: https://issues.jboss.org/browse/WFCORE-3040 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta28 > Reporter: ehsavoie Hugonnet > Assignee: Brian Stansberry > > Currently at stage RUNTIME we check the stepCapabilityStatus before executing the OSH associated with a capability. But this check doesn't take into account the state of the capability dependencies. > For example if we add the undertow subsystem from scratch : the server service is not added because its capability is RELOAD_REQUIRED but when adding the listener the stepCapabilityStatus is NORMAL while it depends on a service that is in RELOAD_REQUIRED so is potentially not there (which is the case) thus the RUNTIME OSH will fail instead of being skipped. > Reproducer: > {code:java} > /extension=org.wildfly.extension.undertow:add(module="org.wildfly.extension.undertow") > /extension=org.wildfly.extension.io:add(module="org.wildfly.extension.io") > batch > /subsystem=undertow:add > /subsystem=undertow/servlet-container=default:add > /subsystem=undertow/server=default-server:add > /subsystem=undertow/server=default-server/host=default-host:add(alias=["localhost"]) > /subsystem=undertow/server=default-server/http-listener=default:add(socket-binding="http") > /subsystem=undertow/buffer-cache=default:add > /subsystem=undertow/configuration=handler:add > /subsystem=undertow/configuration=filter:add > /subsystem=io:add > /subsystem=io/buffer-pool=default:add > /subsystem=io/worker=default:add > /socket-binding-group=standard-sockets/socket-binding=http:add(port="\${jboss.http.port:8080}") > run-batch > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1296) Include LICENSE.txt in META-INF

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1296?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1296: ---------------------------------- Fix Version/s: 1.1.0.CR3 (was: 1.1.0.CR4) > Include LICENSE.txt in META-INF > ------------------------------- > > Key: ELY-1296 > URL: https://issues.jboss.org/browse/ELY-1296 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1296) Include LICENSE.txt in META-INF

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1296?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1296. ----------------------------------- Resolution: Done > Include LICENSE.txt in META-INF > ------------------------------- > > Key: ELY-1296 > URL: https://issues.jboss.org/browse/ELY-1296 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3090) Make script messages around process restarts consistent

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3090?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3090: ------------------------------------------ https://github.com/wildfly/wildfly-core/pull/2631 is what triggered me to file this -- it brings the ps1 behavior to bat. > Make script messages around process restarts consistent > ------------------------------------------------------- > > Key: WFCORE-3090 > URL: https://issues.jboss.org/browse/WFCORE-3090 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Priority: Minor > > The message we output when a process is restarted is inconsistent: > standalone.sh "Restarting application server..." > domain.sh "Restarting JBoss..." > standalone.ps1 "Restarting application server..." (from common.ps1) > domain.ps1 "Restarting application server..." (from common.ps1) > standalone.bat nothing > domain.bat nothing > Problems: > 1) domain.ps1 is inaccurate as it's not just an application server being restarted > 2) The bat files are inconsistent with the others > 3) domain.sh's "Restarting JBoss..." is a bit vague and is odd theoretically given that WildFly Core is meant to be usable for all sorts of things that may not be regarded as "JBoss". > Perhaps just KISS "Restarting..." in all cases? If we want to keep "application server" for the standalone.xxx cases then common.ps1's function will need to have a param added, and then we need to decide a meaningful value for that param (empty text being a valid choice.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3090) Make script messages around process restarts consistent

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3090: ---------------------------------------- Summary: Make script messages around process restarts consistent Key: WFCORE-3090 URL: https://issues.jboss.org/browse/WFCORE-3090 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Brian Stansberry Assignee: Tomaz Cerar Priority: Minor The message we output when a process is restarted is inconsistent: standalone.sh "Restarting application server..." domain.sh "Restarting JBoss..." standalone.ps1 "Restarting application server..." (from common.ps1) domain.ps1 "Restarting application server..." (from common.ps1) standalone.bat nothing domain.bat nothing Problems: 1) domain.ps1 is inaccurate as it's not just an application server being restarted 2) The bat files are inconsistent with the others 3) domain.sh's "Restarting JBoss..." is a bit vague and is odd theoretically given that WildFly Core is meant to be usable for all sorts of things that may not be regarded as "JBoss". Perhaps just KISS "Restarting..." in all cases? If we want to keep "application server" for the standalone.xxx cases then common.ps1's function will need to have a param added, and then we need to decide a meaningful value for that param (empty text being a valid choice.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9119) Don't start GlobalConfiguration services on startup when using non-ha profiles.

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9119?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-12278 to WFLY-9119: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9119 (was: JBEAP-12278) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.ER2) > Don't start GlobalConfiguration services on startup when using non-ha profiles. > ------------------------------------------------------------------------------- > > Key: WFLY-9119 > URL: https://issues.jboss.org/browse/WFLY-9119 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > When starting EAP 7.1.0 ER2 and using *standalone.xml* there are *15% of loaded classes clustering related*. To be precise 1091 classes out of 7285 classes in my check. > *Goal:* > Reduce number of loaded clustering related classes in standalone.xml > Price of 15% of loaded classes for 2nd level cache stuff is too high. > *Logs:* > full log: https://drive.google.com/a/redhat.com/file/d/0BzqZahAZj1YNMDhKb1FDZnF4dlE... .. 20 MB > classes loaded during boot (jboss module logging on trace) aggregated by package name: https://drive.google.com/a/redhat.com/file/d/0BzqZahAZj1YNSFdRWGRFVFdaRXM... > * 445 org.infinispan > * 310 org.wildfly.clustering > * 336 org.jboss.as.clustering > *Details:* > {code} > <logger category="org.jboss.modules"> > <level name="TRACE"/> > </logger> > {code} > {code} > cat server.log | grep "Defined class" | wc -l > 7285 > for i in {2..6}; do echo "Level $i"; cat server.log | grep "Defined class" | sed "s/.*Defined class $.*$/\1/g" \ > | cut -d" " -f 1 | sort | cut -d'.' -f1-$i | uniq -c | sort -n -r | head -n 40; echo ""; done \ > | tee startup-loaded-classes.txt > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Fix Version/s: 1.1.0.CR4 (was: 1.1.0.CR3) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.CR4 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-681) Hide private packages from generated javadoc.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-681?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-681: --------------------------------- Fix Version/s: 1.1.0.CR4 (was: 1.1.0.CR3) > Hide private packages from generated javadoc. > --------------------------------------------- > > Key: ELY-681 > URL: https://issues.jboss.org/browse/ELY-681 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR4 > > > We may want two profiles so we can generate a full javadoc and a 'public' javadoc. > The 'public' javadoc should be the default one generated and should exclude the following packages: - > org.wildfly.security._private > org.wildfly.security.asn1 > org.wildfly.security.auth.realm > org.wildfly.security.auth.realm.* > org.wildfly.security.authz.jacc > org.wildfly.security.credential.store.impl > org.wildfly.security.security.digest > org.wildfly.security.http.impl > org.wildfly.security.security.keystore > org.wildfly.security.mechanism.oauth2 > org.wildfly.security.mechanism.scram > org.wildfly.security.password.impl > org.wildfly.security.password.util > org.wildfly.security.pem > org.wildfly.security.sasl > org.wildfly.security.sasl.* (Except util) > org.wildfly.security.util > org.wildfly.security.util_private > org.wildfly.security.x500 > org.wildfly.security.x500.cert -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-659) Make all mechanism implementations final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-659?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-659: --------------------------------- Fix Version/s: 1.1.0.CR4 (was: 1.1.0.CR3) > Make all mechanism implementations final > ---------------------------------------- > > Key: ELY-659 > URL: https://issues.jboss.org/browse/ELY-659 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Mechanisms, HTTP, SASL > Reporter: David Lloyd > Priority: Critical > Fix For: 1.1.0.CR4 > > > It is very important to make all the mechanism implementations final. Relatedly, they should have no protected members. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-533?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-533: --------------------------------- Fix Version/s: 1.1.0.CR4 (was: 1.1.0.CR3) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.jboss.org/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR4 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 July 2017