September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1800: ---------------------------------- Description: If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. {code} /path=invalid(name=name) {code} For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH. was: If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. {code} /path=invalid(name=name) {code} > Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1800 > URL: https://issues.jboss.org/browse/WFCORE-1800 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1800.patch > > > If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. > Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. > {code} > /path=invalid(name=name) > {code} > For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1800?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1800: ---------------------------------- Attachment: WFCORE-1800.patch > Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1800 > URL: https://issues.jboss.org/browse/WFCORE-1800 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: James Perkins > Assignee: Brian Stansberry > Attachments: WFCORE-1800.patch > > > If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. > Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. > {code} > /path=invalid(name=name) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1800) Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers

by James Perkins (JIRA)

James Perkins created WFCORE-1800: ------------------------------------- Summary: Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers Key: WFCORE-1800 URL: https://issues.jboss.org/browse/WFCORE-1800 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: Brian Stansberry If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. {code} /path=invalid(name=name) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1293) Initialization of inner declaration in accumulate node is not thread safe

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1293: ----------------------------------- Summary: Initialization of inner declaration in accumulate node is not thread safe Key: DROOLS-1293 URL: https://issues.jboss.org/browse/DROOLS-1293 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-623) Checking for anonymous principal by name is insufficient

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-623?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-623: ------------------------------------ Assignee: Jan Kalina (was: Darran Lofthouse) > Checking for anonymous principal by name is insufficient > -------------------------------------------------------- > > Key: ELY-623 > URL: https://issues.jboss.org/browse/ELY-623 > Project: WildFly Elytron > Issue Type: Bug > Reporter: David Lloyd > Assignee: Jan Kalina > > In {{src/main/java/org/wildfly/security/auth/server/SecurityIdentity.java}}: > {noformat} > + if (AnonymousPrincipal.getInstance().getName().equals(name)) { > + if (! context.authorizeAnonymous(false)) { > + throw log.runAsAuthorizationFailed(getPrincipal(), new AnonymousPrincipal(), null); > + } > + } else { > + if (! (context.importIdentity(this) && context.authorize(name, authorize))) { > + throw log.runAsAuthorizationFailed(getPrincipal(), new NamePrincipal(name), null); > + } > } > {noformat} > Only a type check is sufficient to determine if a principal is anonymous. In this fix, the string name "anonymous" takes on a special meaning for the first time, which should not be the case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1292) Initialization of inner declaration in accumulate node is not thread safe

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1292: ----------------------------------- Summary: Initialization of inner declaration in accumulate node is not thread safe Key: DROOLS-1292 URL: https://issues.jboss.org/browse/DROOLS-1292 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-773) ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-773?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-773: ------------------------------------------------ Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1231070|https://bugzilla.redhat.com/show_bug.cgi?id=1231070] from ASSIGNED to NEW > ArrayIndexOutOfBoundsException occurs when a queue-length is 0 in the thread pool executor > -------------------------------------------------------------------------------------------- > > Key: WFCORE-773 > URL: https://issues.jboss.org/browse/WFCORE-773 > Project: WildFly Core > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > BoundedQueueThreadPool does not support zero length queue setup. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7119) Introduce new web session granularity for consistent fine granularity replication

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7119: ---------------------------------- Summary: Introduce new web session granularity for consistent fine granularity replication Key: WFLY-7119 URL: https://issues.jboss.org/browse/WFLY-7119 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 Currently, ATTRIBUTE granularity sessions are vulnerable to partial stale reads, where some session attributes might have current data, and some are stale. For some use cases, this might be intolerable. For these use cases, we should introduce a new session granularity that tracks a version or checksum per attribute, that we can use to detect stale attribute cache entries. This new granularity would retain the performance benefits of ATTRIBUTE granularity replication while maintaining the attribute consistency guarantees of SESSION granularity replication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-1291: ------------------------------------------- Note that all java classes can be executed without any problem > Rule Compilation errors on mac and windows > ------------------------------------------ > > Key: DROOLS-1291 > URL: https://issues.jboss.org/browse/DROOLS-1291 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205) > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Blocker > Attachments: drools_error.png > > > The following error occurs on mac and windows after creating a drools project in Problems view > {code} > Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > Message.GOODBYE cannot be resolved to a type > org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1291) Rule Compilation errors on mac and windows

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1291?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated DROOLS-1291: -------------------------------------- Steps to Reproduce: # Open the wizard for Drools project # Select the option in the middle (a project with examples) # Select a runtime, e.g. BRMS 6.3.0.GA # Press Finish and open Problems view > Rule Compilation errors on mac and windows > ------------------------------------------ > > Key: DROOLS-1291 > URL: https://issues.jboss.org/browse/DROOLS-1291 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Environment: RHDS 10.0.0.GA + RHDSIS 10.0.0.Alpha1 (JBoss Drools 6.4.1.Final-v20160503-1355-B205) > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Blocker > Attachments: drools_error.png > > > The following error occurs on mac and windows after creating a drools project in Problems view > {code} > Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package > Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package > KnowledgeHelper cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > org.kie.api.runtime.rule.FactHandle cannot be resolved to a type > java.lang.Exception cannot be resolved to a type > org.kie.api.runtime.rule.RuleContext cannot be resolved to a type > Message.GOODBYE cannot be resolved to a type > org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type > com.sample.DroolsTest.Message cannot be resolved to a type > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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 September 2016