October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1052) Add server-config parameter to :reload op

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1052?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1052: --------------------------------- Fix Version/s: 2.0.0.Final (was: 2.0.0.CR9) > Add server-config parameter to :reload op > ----------------------------------------- > > Key: WFCORE-1052 > URL: https://issues.jboss.org/browse/WFCORE-1052 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Final > > > {code} > [13:48] Kabir Khan: @BrianStansberry @JasonGreene $./build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/bin/standalone.sh --server-config=20151013-134726769standalone.xml  looks for that file in the snapshots directory > [13:48] Kabir Khan: > [standalone@localhost:9990 /] :list-snapshots > { > "outcome" => "success", > "result" => { > "directory" => "/Users/kabir/sourcecontrol/wildfly/git/wildfly-core/build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/standalone/configuration/standalone_xml_history/snapshot", > "names" => [ > "20151013-134523280standalone.xml", > "20151013-134726769standalone.xml" > ] > } > } > Show less > [13:50] Kabir Khan: server-config should probably be a parameter to the :reload operation > {code} > Similarly we should add host-config and domain-config parameters to the host's reload operation. Using domain-config on a non-DC host should fail. > For a domain server, we should not have the server-config parameter. > We should check the existence of the file before the reload actually is done, or we will end up in a sticky situation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3857) Add JSP logging profile test

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3857?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-3857. ------------------------------- Resolution: Rejected Meh, probably not much point in this. > Add JSP logging profile test > ---------------------------- > > Key: WFLY-3857 > URL: https://issues.jboss.org/browse/WFLY-3857 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > > After WFCORE-101 fix is merged and a release of wildfly-core is done a test needs to be written for logging profiles in JSP's -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-601) Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-601?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-601: --------------------------------------- Assignee: ehsavoie Hugonnet (was: Stuart Douglas) Emmanuel, since you are looking into WFCORE-1074 as well, and Stuart's PR has a CI failure he can't reproduce, can you take this over? Thanks. > Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-601 > URL: https://issues.jboss.org/browse/WFCORE-601 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Stuart Douglas > Assignee: ehsavoie Hugonnet > > I observed this today, looks to be some kind of race in the deployment scanner on boot > {code} > 21:52:08,618 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final > 21:52:10,370 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 21:52:10,440 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting > 21:52:11,390 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 20) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version! > 21:52:11,409 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment mysql-ds.xml > 21:52:11,413 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wildfly-ee7.war > 21:52:11,488 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/48/032d14f289775249a004205c059588ab0f44d4/content > 21:52:11,504 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c6/7babde4791697ddc6509fbd43ba1ec25952d47/content > 21:52:11,506 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wildfly-ee7.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"wildfly-ee7.war\")]" > 21:52:11,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations" > 21:52:11,512 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations\"" > 21:52:11,514 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 21:52:11,514 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1082) CLI module command creates the module.xml main-class element with the incorrect attribute name

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1082?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1082: ---------------------------------- Fix Version/s: 2.0.0.CR9 > CLI module command creates the module.xml main-class element with the incorrect attribute name > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1082 > URL: https://issues.jboss.org/browse/WFCORE-1082 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.0.CR9 > > > The CLI {{module}} command creates the {{modue.xml}} file with the attribute {{value}} for the {{main-class}} element. The attribute should be {{name}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1082) CLI module command creates the module.xml main-class element with the incorrect attribute name

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1082?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1082: ---------------------------------- Priority: Blocker (was: Major) > CLI module command creates the module.xml main-class element with the incorrect attribute name > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1082 > URL: https://issues.jboss.org/browse/WFCORE-1082 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 2.0.0.CR9 > > > The CLI {{module}} command creates the {{modue.xml}} file with the attribute {{value}} for the {{main-class}} element. The attribute should be {{name}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1049) ConcreteResourceRegistration#registerSubModel is not thread safe

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1049?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1049: ------------------------------------- Fix Version/s: 2.0.0.CR9 > ConcreteResourceRegistration#registerSubModel is not thread safe > ---------------------------------------------------------------- > > Key: WFCORE-1049 > URL: https://issues.jboss.org/browse/WFCORE-1049 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Stuart Douglas > Assignee: Brian Stansberry > Fix For: 2.0.0.CR9 > > > registerSubModel checks for existing, then registers, however it is invoked by two threads at the same time it is possible they will both see the resource as not existing and both register. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1082) CLI module command creates the module.xml main-class element with the incorrect attribute name

by James Perkins (JIRA)

James Perkins created WFCORE-1082: ------------------------------------- Summary: CLI module command creates the module.xml main-class element with the incorrect attribute name Key: WFCORE-1082 URL: https://issues.jboss.org/browse/WFCORE-1082 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: James Perkins Assignee: James Perkins The CLI {{module}} command creates the {{modue.xml}} file with the attribute {{value}} for the {{main-class}} element. The attribute should be {{name}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-151) Ability to supply additional information during credential acquisition

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-151?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-151: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Ability to supply additional information during credential acquisition > ---------------------------------------------------------------------- > > Key: ELY-151 > URL: https://issues.jboss.org/browse/ELY-151 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Passwords > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > I think this is the final known gap in our credential acquisition and validation API/SPI. > There are a couple of specifications that also allow for additional information to be used when obtaining a representation of a users credential, the most obvious being the session based variant of digest authentication where a nonce and cnonce are also incorporated. > A second variant with two different modes of operation would be the realm associated with the digest credential, currently we assume it is tightly associated with the storage representation of the credential but it could also be the case that the mech is requesting it for a specific realm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-212) Client-side SSL context configuration is subtly wrong

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-212?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-212: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Client-side SSL context configuration is subtly wrong > ----------------------------------------------------- > > Key: ELY-212 > URL: https://issues.jboss.org/browse/ELY-212 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta3 > > > SSL context client-side configuration is problematic in that the SSL context is not (and cannot be) cached. This means that we lose SSL session reuse and other benefits which may cause problems for users. > However we also cannot just cache an SSL context on a configuration either - the client credentials may vary on each request, causing leakage between identities. > What we need to do is have a separate SSL context client configuration mechanism, and use the generic client context configuration to reference this SSL context client configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-211) Client-side trust store configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-211?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-211: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Client-side trust store configuration > ------------------------------------- > > Key: ELY-211 > URL: https://issues.jboss.org/browse/ELY-211 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta3 > > > Lest I forget. The client needs the ability to supplement the default trust store, to restrict the set of acceptable peer certificates/signers, for mutual authentication purposes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 October 2015