March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2516) Changes to the logging subsystem are not persisted to the logging.properties in offline CLI

by James Perkins (JIRA)

James Perkins created WFCORE-2516: ------------------------------------- Summary: Changes to the logging subsystem are not persisted to the logging.properties in offline CLI Key: WFCORE-2516 URL: https://issues.jboss.org/browse/WFCORE-2516 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins When using {{embed-server}} within offline CLI changes to the logging subsystem are not persisted to the {{logging.properties}} file. Do note that before we fix this we may want to consider a fix for WFCORE-157. The issue being that offline CLI is likely used to provision a server and that server may be configured in a different location. Since the {{jboss.server.log.dir}} or other {{relative-to}} property will be resolved and written as a fully-qualified path this could be an issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-157) Write expressions to logging.properties configuration file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-157?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-157: -------------------------------------- I think this needs to be solved sooner rather than later with a guarantee that only the {{jboss.server.log.dir}} property will be resolvable. This property will need to be passed in the {{JAVA_OPTS}} of all scripts so it is seen during the log manager configuration. We also need to ensure the launcher API passes that specific property as a {{JAVA_OPT}} as well. This will need to be documented to note that if users want to pass non guaranteed properties that these properties must be set in the {{*.conf[.bat|.ps1]}} files. > Write expressions to logging.properties configuration file > ---------------------------------------------------------- > > Key: WFCORE-157 > URL: https://issues.jboss.org/browse/WFCORE-157 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Optional > > Allow properties that use expressions to write the expression out to the logging.properties configuration file. This allows properties passed in at runtime to affect the initial logging configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2515) Upgrade PicketBox to 5.0.0.Beta1

by Stefan Guilhen (JIRA)

Stefan Guilhen created WFCORE-2515: -------------------------------------- Summary: Upgrade PicketBox to 5.0.0.Beta1 Key: WFCORE-2515 URL: https://issues.jboss.org/browse/WFCORE-2515 Project: WildFly Core Issue Type: Task Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2511) overlay, redeploy-links should ignore unknown deployments

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2511?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2511: -------------------------------------- Description: When this operation has been first specified, it has been required to fail if the deployment was not existing. That is not right. Linked deployments can be non existing and a pattern can return an empty set of deployments. The high level operation from the CLI might pass an unexisting deployment name (taking the one from the overlay link to be created for example) which would break the final operation (aka the built composite from the CLI). was: When this operation has been first specified, it has been required to fail if the deployment was not existing. That is not right. Linked deployments can be non existing and a pattern can return an empty set of deployments. > overlay, redeploy-links should ignore unknown deployments > --------------------------------------------------------- > > Key: WFCORE-2511 > URL: https://issues.jboss.org/browse/WFCORE-2511 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Jean-Francois Denise > Assignee: ehsavoie Hugonnet > > When this operation has been first specified, it has been required to fail if the deployment was not existing. That is not right. Linked deployments can be non existing and a pattern can return an empty set of deployments. > The high level operation from the CLI might pass an unexisting deployment name (taking the one from the overlay link to be created for example) which would break the final operation (aka the built composite from the CLI). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2511) overlay, redeploy-links should ignore unknown deployments

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2511?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-2511: ------------------------------------------- Updating design document > overlay, redeploy-links should ignore unknown deployments > --------------------------------------------------------- > > Key: WFCORE-2511 > URL: https://issues.jboss.org/browse/WFCORE-2511 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Jean-Francois Denise > Assignee: ehsavoie Hugonnet > > When this operation has been first specified, it has been required to fail if the deployment was not existing. That is not right. Linked deployments can be non existing and a pattern can return an empty set of deployments. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2514) standalone.sh can hang on gc log back up moves

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2514?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-2514: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1426647 Bugzilla Update: Perform > standalone.sh can hang on gc log back up moves > ---------------------------------------------- > > Key: WFCORE-2514 > URL: https://issues.jboss.org/browse/WFCORE-2514 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Beta7 > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > > If it doesn't have proper write access to an existing backupgc.log, standalone.sh will hang. The file mv should use the -f flag. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-956) Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-956?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev closed ELY-956. ----------------------------- Resolution: Rejected > Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory > ------------------------------------------------------------------------------------------------------------- > > Key: ELY-956 > URL: https://issues.jboss.org/browse/ELY-956 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta24 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Minor > > Coverity static-analysis scan found a synchronization on java.util.concurrent.ConcurrentHashMap object in: > * {{ElytronPolicyConfigurationFactory.getPolicyConfiguration}} > * {{ElytronPolicyConfigurationFactory.inService}} > If policyConfiguration synchronization is concern, it should be enough to synchronize on policyConfiguration object. > > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-956) Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-956?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reopened ELY-956: ------------------------------- > Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory > ------------------------------------------------------------------------------------------------------------- > > Key: ELY-956 > URL: https://issues.jboss.org/browse/ELY-956 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta24 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Minor > > Coverity static-analysis scan found a synchronization on java.util.concurrent.ConcurrentHashMap object in: > * {{ElytronPolicyConfigurationFactory.getPolicyConfiguration}} > * {{ElytronPolicyConfigurationFactory.inService}} > If policyConfiguration synchronization is concern, it should be enough to synchronize on policyConfiguration object. > > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-956) Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-956?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev closed ELY-956. ----------------------------- Resolution: Won't Fix > Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory > ------------------------------------------------------------------------------------------------------------- > > Key: ELY-956 > URL: https://issues.jboss.org/browse/ELY-956 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta24 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Minor > > Coverity static-analysis scan found a synchronization on java.util.concurrent.ConcurrentHashMap object in: > * {{ElytronPolicyConfigurationFactory.getPolicyConfiguration}} > * {{ElytronPolicyConfigurationFactory.inService}} > If policyConfiguration synchronization is concern, it should be enough to synchronize on policyConfiguration object. > > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2379) Synchronize XSD and DMR description of credential-store attributes

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2379?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFCORE-2379: ---------------------------------- Git Pull Request: https://github.com/wildfly-security/elytron-subsystem/pull/444, https://github.com/wildfly-security-incubator/wildfly-core/pull/59 (was: https://github.com/wildfly-security/elytron-subsystem/pull/444) > Synchronize XSD and DMR description of credential-store attributes > ------------------------------------------------------------------ > > Key: WFCORE-2379 > URL: https://issues.jboss.org/browse/WFCORE-2379 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: credential-store > > Use XSD description in DMR description, because description in XSD is better for attributes > * provider-name > * providers > * other-providers > * relative-to > * uri (DMR description contains wrong vault://) > For {{type}} attribute use this description in both XSD and DMR: "The credential store type, e.g. KeyStoreCredentialStore" . Now there is mentioned wrongly KeyStorePasswordStore > {code:xml|title=XSD} > <xs:attribute name="type" type="xs:string" use="optional"> > <xs:annotation> > <xs:documentation> > The credential store type, e.g. KeyStorePasswordStore. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017