jboss-jira June 2017

jboss-jira@lists.jboss.org

1 participants
1955 discussions

[JBoss JIRA] (ELY-1168) Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass.

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/ELY-1168?page=com.atlassian.jira.plugin.s... ] Chao Wang reassigned ELY-1168: ------------------------------ Assignee: Chao Wang (was: Darran Lofthouse) > Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass. > ---------------------------------------------------------------------------------------------------------- > > Key: ELY-1168 > URL: https://issues.jboss.org/browse/ELY-1168 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Chao Wang > > Wildfly Elytron Tool, credential-store command "add" option with --entry-type without argument value pass. > It seems to be little confusing. I prefer error message rather than success. > Reason why it works now is because as a value is used default value for entry-type. > *How to reproduce* > {code} > java -jar ./bin/wildfly-elytron-tool.jar credential-store --add secret_alias --create -l store123.jceks --password pass123 -x test -n > Alias "secret_alias" has been successfully stored > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by John Ament (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] John Ament commented on WFLY-8488: ---------------------------------- [~rhusar] ping? :-) > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2895) Save memory in RuntimeCapability ServiceName creation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2895: ------------------------------------- Summary: Save memory in RuntimeCapability ServiceName creation (was: Save memory in dynamic RuntimeCapability ServiceName creation) > Save memory in RuntimeCapability ServiceName creation > ----------------------------------------------------- > > Key: WFCORE-2895 > URL: https://issues.jboss.org/browse/WFCORE-2895 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. > Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2895) Save memory in dynamic RuntimeCapability ServiceName creation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2895: ------------------------------------- Description: RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. was: RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. > Save memory in dynamic RuntimeCapability ServiceName creation > ------------------------------------------------------------- > > Key: WFCORE-2895 > URL: https://issues.jboss.org/browse/WFCORE-2895 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates its ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. > Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2895) Save memory in dynamic RuntimeCapability ServiceName creation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2895: ------------------------------------- Description: RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. was: RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. Also RuntimeCapability should not create a ServiceName even if the cap has no serviceValueType. > Save memory in dynamic RuntimeCapability ServiceName creation > ------------------------------------------------------------- > > Key: WFCORE-2895 > URL: https://issues.jboss.org/browse/WFCORE-2895 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates it's ServiceName by parsing the base capability's string name instead of using its existing ServiceName. This wastes memory since the strings end up being duplicated. > Also RuntimeCapability should not create a ServiceName if the cap has no serviceValueType. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

← Newer
1
...
193
194
195
196
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2017