September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7120) NPE in SessionManagerStatsHandler

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/WFLY-7120?page=com.atlassian.jira.plugin.... ] Mathieu Lachance commented on WFLY-7120: ---------------------------------------- The pull request has been merged 4h ago by [~kabirkhan], should I set the issue status to 'resolved' ? > NPE in SessionManagerStatsHandler > --------------------------------- > > Key: WFLY-7120 > URL: https://issues.jboss.org/browse/WFLY-7120 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Brian Stansberry > Assignee: Mathieu Lachance > > [~matlach] reports an NPE when SessionManagerStatsHandler tries to use the ServiceController for a no-longer present deployment. See https://github.com/wildfly/wildfly/pull/9189 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1803) CLI tests to modify history file located in user home directory

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1803?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1803: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1805 > CLI tests to modify history file located in user home directory > --------------------------------------------------------------- > > Key: WFCORE-1803 > URL: https://issues.jboss.org/browse/WFCORE-1803 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha8 > > > These tests must set the user.home var to Temporary Location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1804: ---------------------------------------------- This is an Aesh behavior. Aesh expects quotes and double quotes to be escaped: # test \" <return> works fine. > CLI comments are not ended at the end of line > --------------------------------------------- > > Key: WFCORE-1804 > URL: https://issues.jboss.org/browse/WFCORE-1804 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Jean-Francois Denise > > *Description of problem:* > * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes. > * This is regression against EAP 6.4.x > *How reproducible:* > Always > *Steps to Reproduce + Actual results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > > > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > > > {noformat} > *Expected results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > [standalone@localhost:9990 /] > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > [standalone@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7125) Required attributes of elytron key-store creation CLI command

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7125?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-7125: ------------------------------- Description: Minimal CLI command to create key store is {code} /subsystem=elytron/key-store=server:add(type="JKS") {code} But it has these problems: * Password attribute has to be required. I can't think of case when that could be ommited. * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description. was: Minimal CLI command to create key store is {code} /subsystem=elytron/key-store=server:add(type="JKS") {code} But it has these problems: * Command let me create jks keystore without {{path}} specified. It is because {{required}} attribute is default to false. I can think of 2 {{required=false}} usages: PKCS11 some sort of dynamic key-store creation in runtime But that looks to me as less common cases. I think dominantlly user will use file-based key store type with existing keystore. So I would propose to change default {{required}} default to true. * Password attribute has to be required. I can't think of case when that could be ommited. * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description. In result it will be possible to create key-store by this minimal CLI command: {code} /subsystem=elytron/key-store=server:add(path="server.jks", password="secret") {code} > Required attributes of elytron key-store creation CLI command > ------------------------------------------------------------- > > Key: WFLY-7125 > URL: https://issues.jboss.org/browse/WFLY-7125 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > > Minimal CLI command to create key store is > {code} > /subsystem=elytron/key-store=server:add(type="JKS") > {code} > But it has these problems: > * Password attribute has to be required. I can't think of case when that could be ommited. > * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ] Alexey Loubyansky reassigned WFCORE-1804: ----------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) Jeff, could you please investigate? Thanks! > CLI comments are not ended at the end of line > --------------------------------------------- > > Key: WFCORE-1804 > URL: https://issues.jboss.org/browse/WFCORE-1804 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Jean-Francois Denise > > *Description of problem:* > * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes. > * This is regression against EAP 6.4.x > *How reproducible:* > Always > *Steps to Reproduce + Actual results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > > > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > > > {noformat} > *Expected results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > [standalone@localhost:9990 /] > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > [standalone@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1804) CLI comments are not ended at the end of line

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1804?page=com.atlassian.jira.plugi... ] Alexey Loubyansky moved JBEAP-6038 to WFCORE-1804: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1804 (was: JBEAP-6038) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) > CLI comments are not ended at the end of line > --------------------------------------------- > > Key: WFCORE-1804 > URL: https://issues.jboss.org/browse/WFCORE-1804 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > *Description of problem:* > * CLI comments are not ended at the end of line, if it contains quotation marks or apostrophes. > * This is regression against EAP 6.4.x > *How reproducible:* > Always > *Steps to Reproduce + Actual results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > > > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > > > {noformat} > *Expected results:* > {noformat} > [standalone@localhost:9990 /] # test ' test > [standalone@localhost:9990 /] > {noformat} > {noformat} > [standalone@localhost:9990 /] # what " what > [standalone@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-630) Elytron - aggregate-role-mapper can contain multi reference to one role mapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-630?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-630: -------------------------------------- As I have mentioned elsewhere I don't think this is necessarily an invalid configuration - as administrators can plug in custom implementations there is always a possibility that they may want their implementation repeating. > Elytron - aggregate-role-mapper can contain multi reference to one role mapper > ------------------------------------------------------------------------------ > > Key: ELY-630 > URL: https://issues.jboss.org/browse/ELY-630 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Minor > > Aggregate-role-mapper can contain multi reference to one role mapper. > In my opinion it isn't valid state. > But there is some probability that it is required behaviour. > Can you have a look on it? > Configuration snippet: > {code} > <subsystem xmlns="urn:wildfly:elytron:1.0"> > <mappers> > <add-prefix-role-mapper name="CreaperTestAddPrefixRoleMapper" prefix="somePrefix"/> > <aggregate-role-mapper name="CreaperTestAggregateRoleMapper"> > <role-mapper name="CreaperTestAddPrefixRoleMapper"/> > <role-mapper name="CreaperTestAddPrefixRoleMapper"/> > </aggregate-role-mapper> > </mappers> > </subsystem> > {code} > *Actual results:* > Aggregate-role-mapper can contain multi reference to one role-mapper. > *Expected results:* > You would not be able to define multi reference to one role-mapper in aggregate-role-mapper. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2640) Unable to add cached-connection-manager after removing it once

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-2640?page=com.atlassian.jira.plugin.... ] Ingo Weiss commented on WFLY-2640: ---------------------------------- I will take a look at this one > Unable to add cached-connection-manager after removing it once > -------------------------------------------------------------- > > Key: WFLY-2640 > URL: https://issues.jboss.org/browse/WFLY-2640 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Masafumi Miura > > {{<cached-connection-manager>}} is enabled in jca subsystem by default: > {code:xml} > <subsystem xmlns="urn:jboss:domain:jca:1.1"> > ... > <cached-connection-manager /> > </subsystem> > {code} > However, it is unable to re-enable {{<cached-connection-manager>}} once it is disabled. CLI command fails to add it due to duplicate resource. > {code} > [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:remove > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] :reload > { > "outcome" => "success", > "result" => undefined > } > [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:add > { > "outcome" => "failed", > "failure-description" => "JBAS014803: Duplicate resource [ > (\"subsystem\" => \"jca\"), > (\"cached-connection-manager\" => \"cached-connection-manager\") > ]", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7125) Required attributes of elytron key-store creation CLI command

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7125?page=com.atlassian.jira.plugin.... ] Martin Choma moved JBEAP-6035 to WFLY-7125: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7125 (was: JBEAP-6035) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR4) > Required attributes of elytron key-store creation CLI command > ------------------------------------------------------------- > > Key: WFLY-7125 > URL: https://issues.jboss.org/browse/WFLY-7125 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > > Minimal CLI command to create key store is > {code} > /subsystem=elytron/key-store=server:add(type="JKS") > {code} > But it has these problems: > * Command let me create jks keystore without {{path}} specified. It is because {{required}} attribute is default to false. I can think of 2 {{required=false}} usages: > PKCS11 > some sort of dynamic key-store creation in runtime > But that looks to me as less common cases. I think dominantlly user will use file-based key store type with existing keystore. So I would propose to change default {{required}} default to true. > * Password attribute has to be required. I can't think of case when that could be ommited. > * Attribute {{type}} could be optional. If not set default value can be Keystore.getDefaultType(). As model cant't express this, it can be documented in description. > In result it will be possible to create key-store by this minimal CLI command: > {code} > /subsystem=elytron/key-store=server:add(path="server.jks", password="secret") > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1803) CLI tests to modify history file located in user home directory

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-1803: -------------------------------------------- Summary: CLI tests to modify history file located in user home directory Key: WFCORE-1803 URL: https://issues.jboss.org/browse/WFCORE-1803 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise These tests must set the user.home var to Temporary Location. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016