January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2287) Thread safety issues and race conditions in VERIFY_SUSPECT

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2287?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2287. ---------------------------- Resolution: Done [~pferraro] Take a look as see if this fixes your issue(s) > Thread safety issues and race conditions in VERIFY_SUSPECT > ---------------------------------------------------------- > > Key: JGRP-2287 > URL: https://issues.jboss.org/browse/JGRP-2287 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.13 > Reporter: Paul Ferraro > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.16 > > > While addressing JGRP-2286, I noticed a number of thread safety issues and race conditions in VERIFY_SUSPECT, e.g. > 1. "suspects" DelayQueue is accessed concurrently within synchronized block by most of the code, however, the run() method calls isEmpty(), size(), and most notably, drainTo(...) without sufficient exclusivity. drainTo is particularly problematic in the case of concurrent modifications. > 2. "timer" Thread is non-volatile, but its reference is set by multiple threads. > 3. The startTimer() method only creates a new thread if Thread.isAlive() returns false. However, if the thread is just completing (i.e. exiting its loop), this method can return true, and the verification of suspected members can be delayed until the next suspect event. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3478) drlx-parser contains content of javax.annotation-api

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3478?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-3478. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drlx-parser/commit/ffb508c9b8a6d892f25ca3c0ab... > drlx-parser contains content of javax.annotation-api > ---------------------------------------------------- > > Key: DROOLS-3478 > URL: https://issues.jboss.org/browse/DROOLS-3478 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.16.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Critical > > Artifact drlx-parser contains classes from javax.annotation-api. These classes were brought by https://github.com/kiegroup/drlx-parser/commit/e100effcad56d6715e18c9840d... . > These classes cause classpath issues to Kie server deployed on WebSphere, causing failures in JMS functionality. > Please remove javax.annotation-api classes from drlx-parser. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2287) Thread safety issues and race conditions in VERIFY_SUSPECT

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2287?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2287 at 1/9/19 6:07 AM: -------------------------------------------------------- Re 1: {{DelayQueue}} is synchronized, so why should this be a problem? Re 2: {{timer}} was set to {{volatile}} by a PR Re 3: I changed the code slightly, so that adding to the queue and setting {{running}} is done atomically, pluschecking for the empty queue in {{run()}} and setting {{running=false}} is also done atomically. was (Author: belaban): Re 1: {{DelayQueue}} is synchronized, so why should this be a problem? Re 2: {{timer}} was set to {{volatile}} by a PR > Thread safety issues and race conditions in VERIFY_SUSPECT > ---------------------------------------------------------- > > Key: JGRP-2287 > URL: https://issues.jboss.org/browse/JGRP-2287 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.13 > Reporter: Paul Ferraro > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.16 > > > While addressing JGRP-2286, I noticed a number of thread safety issues and race conditions in VERIFY_SUSPECT, e.g. > 1. "suspects" DelayQueue is accessed concurrently within synchronized block by most of the code, however, the run() method calls isEmpty(), size(), and most notably, drainTo(...) without sufficient exclusivity. drainTo is particularly problematic in the case of concurrent modifications. > 2. "timer" Thread is non-volatile, but its reference is set by multiple threads. > 3. The startTimer() method only creates a new thread if Thread.isAlive() returns false. However, if the thread is just completing (i.e. exiting its loop), this method can return true, and the verification of suspected members can be delayed until the next suspect event. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshit API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-554: ------------------------------------ Assignee: Hayk Hovsepyan (was: Michael Foley) > Add missing Openshit API calls > ------------------------------ > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshit API calls

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-554: ------------------------------------ Summary: Add missing Openshit API calls Key: SWSQE-554 URL: https://issues.jboss.org/browse/SWSQE-554 Project: Kiali QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. 1. Figure out which calls are missing to Openshift. 2. Create API call. 3. Create assertions on that results to compare with UI data. 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2262: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] DRD Grid Column width is not preserved > ----------------------------------------------------- > > Key: DROOLS-2262 > URL: https://issues.jboss.org/browse/DROOLS-2262 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > DND Grid Column don't preserve the width. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3481) Data type constraints: DMN canvas view workflow

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3481?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3481: ---------------------------------------- [~uxdlc] Looks good to me. [~karreiro] Do you think we'd be able to re-use the _constraint_ widgets from the Data Types tab? (I'd like to be able to!) > Data type constraints: DMN canvas view workflow > ----------------------------------------------- > > Key: DROOLS-3481 > URL: https://issues.jboss.org/browse/DROOLS-3481 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * Provide options for: > - one-off constraints > - apply constraints to data type. > - possibly "yoke" constraints to data type. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > * Maintain "Manage" link. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11479) HTTP Basic Authentication - Silent Operation

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFLY-11479?page=com.atlassian.jira.plugin... ] Martin Choma updated WFLY-11479: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11990 > HTTP Basic Authentication - Silent Operation > -------------------------------------------- > > Key: WFLY-11479 > URL: https://issues.jboss.org/browse/WFLY-11479 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 16.0.0.Beta1 > > > Using HTTP Basic authentication with Undertow it was possible to switch into a silent mode where an incoming header could be processed but clients would not be challenged - this RFE is to support the same behaviour with WildFly Elytron. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3429) Serialization of KiePackages fails when SecurityManager is enabled

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3429?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-3429: --------------------------------------- [~aboukhal] I am afraid we missed the 7.16.0.Final release, so it will be in 7.17.0.Final, which should be out in a month or so, if nothing blocking happens. We try to release each month now [1]. [1] https://mvnrepository.com/artifact/org.drools/drools-core > Serialization of KiePackages fails when SecurityManager is enabled > ------------------------------------------------------------------ > > Key: DROOLS-3429 > URL: https://issues.jboss.org/browse/DROOLS-3429 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.15.0.Final > Environment: Running with IBM JDK 1.8 > Reporter: Marcel Abou Khalil > Assignee: Tibor Zimányi > Priority: Major > Fix For: 7.17.0.Final > > > Our Drools setup: > - users write rules in a combination of DSL and Java code > - rules are compiled > - packages are stored in a database (rules are seldom changed but often ran) > This has been working fine but in order to improve security, we've enabled the SecurityManager. This throws an exception while trying to serialize the consequence part of the rule: > {code:java} > Caused by: java.io.NotSerializableException: com.redacted.Rule_Events_REDACTED61028857611DefaultConsequenceInvoker > - field (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", name: "delegate", type: "interface org.drools.core.spi.Consequence") > - object (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence@93071816) > - writeExternal data > - object (class "org.drools.core.definitions.rule.impl.RuleImpl", [Rule name=REDACTED, agendaGroup=end, salience=0, no-loop=true]) > - writeExternal data > - object (class "org.drools.core.rule.JavaDialectRuntimeData", org.drools.core.rule.JavaDialectRuntimeData{...}) > - custom writeObject data (class "java.util.HashMap") > - object (class "java.util.HashMap", {java=org.drools.core.rule.JavaDialectRuntimeData{...}, mvel=org.drools.core.rule.MVELDialectRuntimeData@b99ea6b2}) > - writeExternal data > - root object (class "org.drools.core.rule.DialectRuntimeRegistry", org.drools.core.rule.DialectRuntimeRegistry@2d9acae8) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1213) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1615) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1576) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1499) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1209) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:365) > at org.drools.core.definitions.rule.impl.RuleImpl.writeExternal(RuleImpl.java:180) > {code} > Possible cause: > Class {{RuleImpl}}, method {{writeExternal}} will write out {{null}} if the consequence is of type {{CompiledInvoker}}. But if the SecurityManager is enabled, the method {{wire}} will wrap the Consequence inside a {{SafeConsequence}}. A {{SafeConsequence}}, in contrast to the wrapped consequence is not a {{CompiledInvoker}}, so {{writeExternal}} will attempt to serialize it, instead of just writing {{null}} and fails. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11575) DefaultCacheContainer getCache(...) createIfAbsent variants throw NPE when called with false and cache does not exist

by Luís Cabral (Jira)

[ https://issues.jboss.org/browse/WFLY-11575?page=com.atlassian.jira.plugin... ] Luís Cabral edited comment on WFLY-11575 at 1/9/19 3:25 AM: ------------------------------------------------------------ ??Affects Version/s?? - 13.0.0.Final as well Stacktrace: {code:java} Caused by: java.lang.NullPointerException at org.jboss.as.clustering.infinispan.DefaultCacheContainer.wrap(DefaultCacheContainer.java:107) at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:97) {code} was (Author: narlong): ??Affects Version/s?? - 13.0.0.Final as well > DefaultCacheContainer getCache(...) createIfAbsent variants throw NPE when called with false and cache does not exist > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11575 > URL: https://issues.jboss.org/browse/WFLY-11575 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 15.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019