December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3453) Upgrade JBoss Build Tools to 1.2.3.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3453: ----------------------------------- Summary: Upgrade JBoss Build Tools to 1.2.3.Final Key: WFCORE-3453 URL: https://issues.jboss.org/browse/WFCORE-3453 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2172) Segment split can cause the resulting segments to be associated to the wrong path

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2172?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2172: -------------------------------- Sprint: 2017 Week 49-50 > Segment split can cause the resulting segments to be associated to the wrong path > --------------------------------------------------------------------------------- > > Key: DROOLS-2172 > URL: https://issues.jboss.org/browse/DROOLS-2172 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2172) Segment split can cause the resulting segments to be associated to the wrong path

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2172?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2172: ------------------------------------- If a segment split happens during an incremental compilation all the paths associated to the old segment are also associated to the new one regardless if the new segment actually belongs to that path or not. This may lead to spurious path linking and then to a NPE when the whole path is evaluated like the following {code} java.lang.NullPointerException at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:114) at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87) at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34) at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43) at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067) at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1320) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1311) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1295) {code} > Segment split can cause the resulting segments to be associated to the wrong path > --------------------------------------------------------------------------------- > > Key: DROOLS-2172 > URL: https://issues.jboss.org/browse/DROOLS-2172 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2172) Segment split can cause the resulting segments to be associated to the wrong path

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2172: ----------------------------------- Summary: Segment split can cause the resulting segments to be associated to the wrong path Key: DROOLS-2172 URL: https://issues.jboss.org/browse/DROOLS-2172 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Edson Tirelli -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2172) Segment split can cause the resulting segments to be associated to the wrong path

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2172?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-2172: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Segment split can cause the resulting segments to be associated to the wrong path > --------------------------------------------------------------------------------- > > Key: DROOLS-2172 > URL: https://issues.jboss.org/browse/DROOLS-2172 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2172) Segment split can cause the resulting segments to be associated to the wrong path

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2172?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2172: -------------------------------- Component/s: core engine > Segment split can cause the resulting segments to be associated to the wrong path > --------------------------------------------------------------------------------- > > Key: DROOLS-2172 > URL: https://issues.jboss.org/browse/DROOLS-2172 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2163) [DMN Editor] Context table doesn't show entry type label if table is scrolled

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2163?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2163: ---------------------------------------- See https://github.com/manstis/kie-wb-common/commit/1cfeb6ad954a91cc8764f65e1... > [DMN Editor] Context table doesn't show entry type label if table is scrolled > ----------------------------------------------------------------------------- > > Key: DROOLS-2163 > URL: https://issues.jboss.org/browse/DROOLS-2163 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > > Context table offers 5 types of entries while each entry has label of its own type (Literal Expression, Function Relation etc.) However this label is not shown if the user scroll the table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2163) [DMN Editor] Context table doesn't show entry type label if table is scrolled

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2163?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2163. ------------------------------------ Resolution: Done > [DMN Editor] Context table doesn't show entry type label if table is scrolled > ----------------------------------------------------------------------------- > > Key: DROOLS-2163 > URL: https://issues.jboss.org/browse/DROOLS-2163 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > > Context table offers 5 types of entries while each entry has label of its own type (Literal Expression, Function Relation etc.) However this label is not shown if the user scroll the table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-34) Automation Testcase

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-34?page=com.atlassian.jira.plu... ] Vojtech Prusa closed HAWKULARQE-34. ----------------------------------- Resolution: Out of Date > Automation Testcase > ------------------- > > Key: HAWKULARQE-34 > URL: https://issues.jboss.org/browse/HAWKULARQE-34 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Vojtech Prusa > Priority: Critical > > Smoke automation test to add new middleware provider with SSL and check that inventory is loaded. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3448) Unable to set multiple ssl protocols and ciphers on security-realms using system properties

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3448?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3448: ---------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2972, https://github.com/wildfly/wildfly-core/pull/2973 (was: https://github.com/wildfly/wildfly-core/pull/2972) > Unable to set multiple ssl protocols and ciphers on security-realms using system properties > ------------------------------------------------------------------------------------------- > > Key: WFCORE-3448 > URL: https://issues.jboss.org/browse/WFCORE-3448 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Derek Horton > Assignee: Brian Stansberry > > It is not possible to set the ssl protocol and ciphers on a security-realm using system property if multiple protocols and/or ciphers are needed. > Setting the "enabled-cipher-suites" and "enabled-protocols" using a system property works if the system property value resolves to a single value ("TLSv1.2" for example). > An error is thrown if the system property has multiple values (-Dtlsversion="TLSv1.1 TLSv1.2"). Here is the error that is generated: > 13:20:43,315 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ManagementRealm.ssl-context: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ManagementRealm.ssl-context: WFLYDM0096: No protocols in common, supported=([SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2]), requested=([TLSv1.1 TLSv1.2]) > at org.jboss.as.domain.management.security.SSLContextService.wrapSslContext(SSLContextService.java:137) > at org.jboss.as.domain.management.security.SSLContextService.start(SSLContextService.java:102) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 December 2017