November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7476) Complicated failure-descriptions in Elytron properties-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7476?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7476: ---------------------------------- "WFLYCTL0180: Services with missing/unavailable dependencies" is unneeded, but it is not generated by elytron but by jboss-msc. Cannot be removed. > Complicated failure-descriptions in Elytron properties-realm > ------------------------------------------------------------ > > Key: WFLY-7476 > URL: https://issues.jboss.org/browse/WFLY-7476 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: user_experience > > There are complicated failure-descriptions in Elytron properties-realm. They include some details from exceptions which are not needed and can be confused for non-java administrators. Please handle these exceptions and provide some user friendly failure-description. > Examples of complicated failure-description in properties-realm: > * Adding path which does not exist: > {code} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=/wrong/path/a.properties}) > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm. > Caused by: java.io.FileNotFoundException: /wrong/path/a.properties (No such file or directory)"}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > }, > "rolled-back" => true > } > {code} > * Adding file with missing $REALM: > {code} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=/some/path/roles.properties}) > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0080: Failed services" => {"org.wildfly.security.security-realm.realm" => "org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.realm: WFLYELY00014: Unable to load the properties files required to start the properties file backed realm. > Caused by: java.io.IOException: ELY01006: No realm name found in properties file"}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.realm"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > }, > "rolled-back" => true > } > {code} > * path mentiond in relative-to does not exist: > {code} > /subsystem=elytron/properties-realm=realm:add(users-properties={path=users.properties,relative-to=non.exist}) > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-realm.realm is missing [jboss.server.path.\"non.exist\"]"] > }, > "rolled-back" => true > } > {code} > Suggestion for improvement: > * use only description of failure, e.g. something like "file /wrong/path/a.properties was not found" > * do not use any unneeded information - e.g. "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7529) Singleton subsystem remove operation must require reload

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7529?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-7529: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Paul Ferraro) > Singleton subsystem remove operation must require reload > -------------------------------------------------------- > > Key: WFLY-7529 > URL: https://issues.jboss.org/browse/WFLY-7529 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Dmitrii Tikhomirov > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7528) Infinispan subsystem remove operation must require reload

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-7528?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-7528: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Paul Ferraro) > Infinispan subsystem remove operation must require reload > --------------------------------------------------------- > > Key: WFLY-7528 > URL: https://issues.jboss.org/browse/WFLY-7528 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Dmitrii Tikhomirov > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-931) PicketBoxMessages.authorizationFailedMessage misspelled Acces => Access

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-931?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-931: -------------------------------------------------- Ivo Hradek <ihradek(a)redhat.com> changed the Status of [bug 1387278|https://bugzilla.redhat.com/show_bug.cgi?id=1387278] from ON_QA to VERIFIED > PicketBoxMessages.authorizationFailedMessage misspelled Acces => Access > ----------------------------------------------------------------------- > > Key: SECURITY-931 > URL: https://issues.jboss.org/browse/SECURITY-931 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Minor > > Acces should be Access in : > security-spi/common/src/main/java/org/jboss/security/PicketBoxMessages.java: @Message(id = 17, value = "Acces denied: authorization failed") -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7541) If message-load-balancing-type is STRICT then redistribution does not work

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7541?page=com.atlassian.jira.plugin.... ] Miroslav Novak reopened WFLY-7541: ---------------------------------- > If message-load-balancing-type is STRICT then redistribution does not work > -------------------------------------------------------------------------- > > Key: WFLY-7541 > URL: https://issues.jboss.org/browse/WFLY-7541 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Miroslav Novak > Assignee: Justin Bertram > > If cluster connection is configured with STRICT load-balancing policy like: > {code}<cluster-connection name="my-cluster" discovery-group="dg-group1" retry-interval="1000" connector-name="http-connector" address="jms" message-load-balancing-type="STRICT"/> > {code} > then redistribution is disabled as a side effect. Message redistribution should be configured only by value for {{redelivery-delay}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2127) UnicastHeader3: reduce in-memory size

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2127?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2127. ---------------------------- Resolution: Rejected Reduced the size of UnicastHeader3 by 8 bytes > UnicastHeader3: reduce in-memory size > ------------------------------------- > > Key: JGRP-2127 > URL: https://issues.jboss.org/browse/JGRP-2127 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > JOL reports: > {noformat} > org.jgroups.protocols.UnicastHeader3 object internals: > OFFSET SIZE TYPE DESCRIPTION VALUE > 0 4 (object header) 01 00 00 00 (00000001 00000000 00000000 00000000) (1) > 4 4 (object header) 00 00 00 00 (00000000 00000000 00000000 00000000) (0) > 8 4 (object header) 9d 11 01 f8 (10011101 00010001 00000001 11111000) (-134147683) > 12 2 short Header.prot_id 0 > 14 2 (alignment/padding gap) N/A > 16 8 long UnicastHeader3.seqno 0 > 24 8 long UnicastHeader3.timestamp 0 > 32 2 short UnicastHeader3.conn_id 0 > 34 1 byte UnicastHeader3.type 0 > 35 1 boolean UnicastHeader3.first false > 36 4 (loss due to the next object alignment) > Instance size: 40 bytes > Space losses: 2 bytes internal + 4 bytes external = 6 bytes total > {noformat} > We could reduce the size to 32 by making {{timestamp}} an int. This field is used for comparison against previous timestamps, and since the comparison takes numeric overflow into account, wrap-around is not a problem. > After the change of {{timestamp}} from {{long}} -> {{int}}: > {noformat} > org.jgroups.protocols.UnicastHeader3 object internals: > OFFSET SIZE TYPE DESCRIPTION VALUE > 0 4 (object header) 01 00 00 00 (00000001 00000000 00000000 00000000) (1) > 4 4 (object header) 00 00 00 00 (00000000 00000000 00000000 00000000) (0) > 8 4 (object header) 9d 11 01 f8 (10011101 00010001 00000001 11111000) (-134147683) > 12 2 short Header.prot_id 0 > 14 2 (alignment/padding gap) N/A > 16 8 long UnicastHeader3.seqno 0 > 24 4 int UnicastHeader3.timestamp 0 > 28 2 short UnicastHeader3.conn_id 0 > 30 1 byte UnicastHeader3.type 0 > 31 1 boolean UnicastHeader3.first false > Instance size: 32 bytes > Space losses: 2 bytes internal + 0 bytes external = 2 bytes total > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7541) If message-load-balancing-type is STRICT then redistribution does not work

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7541?page=com.atlassian.jira.plugin.... ] Miroslav Novak moved JBEAP-4288 to WFLY-7541: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7541 (was: JBEAP-4288) Issue Type: Feature Request (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.1.0.Final (was: 7.0.0.CR1) > If message-load-balancing-type is STRICT then redistribution does not work > -------------------------------------------------------------------------- > > Key: WFLY-7541 > URL: https://issues.jboss.org/browse/WFLY-7541 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Miroslav Novak > Assignee: Justin Bertram > > If cluster connection is configured with STRICT load-balancing policy like: > {code}<cluster-connection name="my-cluster" discovery-group="dg-group1" retry-interval="1000" connector-name="http-connector" address="jms" message-load-balancing-type="STRICT"/> > {code} > then redistribution is disabled as a side effect. Message redistribution should be configured only by value for {{redelivery-delay}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7540) Not possible to lookup exported JMS resources by full JNDI name with java:jboss/exported/... prefix

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7540?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-7540: --------------------------------- Labels: user_experience (was: ) > Not possible to lookup exported JMS resources by full JNDI name with java:jboss/exported/... prefix > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-7540 > URL: https://issues.jboss.org/browse/WFLY-7540 > Project: WildFly > Issue Type: Enhancement > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Miroslav Novak > Assignee: David Lloyd > Labels: user_experience > > If exported queue/topic or connection factory is looked up from JNDI by remote client then client must use relative JNDI name. > For example if queue is registrered in JNDI under name {{java:jboss/exported/jms/queue/InQueue}} then client must lookup {{jms/queue/InQueue}} > In case client tries to lookup queue by full JNDI name {{java:jboss/exported/jms/queue/InQueue}} then lookup fails with exception: {code} > javax.naming.NameNotFoundException: jboss/exported/jms/queue/InQueue -- service jboss.naming.context.java.jboss.exported.jboss.exported.jms.queue.InQueue > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) ~[na:na] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) ~[na:na] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) ~[na:na] > at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) ~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final] > at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) ~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_51] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7540) Not possible to lookup exported JMS resources by full JNDI name with java:jboss/exported/... prefix

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7540?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-7540: -------------------------------------- [~dmlloyd] I'm not sure if you're the right assignee for this. It seems that this should be on todo list for JNDI. wdyt? > Not possible to lookup exported JMS resources by full JNDI name with java:jboss/exported/... prefix > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-7540 > URL: https://issues.jboss.org/browse/WFLY-7540 > Project: WildFly > Issue Type: Enhancement > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Miroslav Novak > Assignee: David Lloyd > Labels: user_experience > > If exported queue/topic or connection factory is looked up from JNDI by remote client then client must use relative JNDI name. > For example if queue is registrered in JNDI under name {{java:jboss/exported/jms/queue/InQueue}} then client must lookup {{jms/queue/InQueue}} > In case client tries to lookup queue by full JNDI name {{java:jboss/exported/jms/queue/InQueue}} then lookup fails with exception: {code} > javax.naming.NameNotFoundException: jboss/exported/jms/queue/InQueue -- service jboss.naming.context.java.jboss.exported.jboss.exported.jms.queue.InQueue > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) ~[na:na] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) ~[na:na] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) ~[na:na] > at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) ~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final] > at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) ~[jboss-remote-naming-2.0.4.Final.jar:2.0.4.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_51] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Jan Kalina closed WFLY-7396. ---------------------------- Resolution: Done No more similar problems found, closing. > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016