December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3413) CME in DefaultAgenda.evaluateEagerList

by Will Keaney (Jira)

Will Keaney created DROOLS-3413: ----------------------------------- Summary: CME in DefaultAgenda.evaluateEagerList Key: DROOLS-3413 URL: https://issues.jboss.org/browse/DROOLS-3413 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Environment: RHEL 6.10 x86_64 Drools embedded in OpenNMS Meridian 2017.1.5. Reporter: Will Keaney Assignee: Mario Fusco I have a KieSession that runs in Stream processing mode, which is throwing frequent ConcurrentModificationExceptions in evaluateEagerList: {code}Exception in thread "FireTask" java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at java.util.ArrayList$Itr.next(ArrayList.java:851) at org.drools.core.phreak.PhreakFromNode.doLeftUpdates(PhreakFromNode.java:176) at org.drools.core.phreak.PhreakFromNode.doNode(PhreakFromNode.java:64) at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:355) at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:301) at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:136) at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:94) at org.drools.core.phreak.RuleExecutor.evaluateNetwork(RuleExecutor.java:65) at org.drools.core.common.DefaultAgenda.evaluateEagerList(DefaultAgenda.java:983) at org.drools.core.phreak.RuleExecutor.haltRuleFiring(RuleExecutor.java:233) at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:138) at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:970) at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1312) at org.drools.core.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1232) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1398) at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1377) at org.opennms.netmgt.correlation.drools.DroolsCorrelationEngine.lambda$initialize$2(DroolsCorrelationEngine.java:217) at java.lang.Thread.run(Thread.java:745){code} Many of the rules in this KB have {{no-loop true}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11480) Possible to remove referenced activemq http-connector

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11480?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11480: --------------------------------------- Component/s: JMS Assignee: ehsavoie Hugonnet (was: Jason Greene) > Possible to remove referenced activemq http-connector > ----------------------------------------------------- > > Key: WFLY-11480 > URL: https://issues.jboss.org/browse/WFLY-11480 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 15.0.0.Final > Reporter: Marcel Šebek > Assignee: ehsavoie Hugonnet > Priority: Major > > It is possible to remove activemq http-connector that is referenced by broadcast-group, leading to crash on server next boot: > 18:30:52,360 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 81) MSC000001: Failed to start service jboss.messaging-activemq.default.jms.connection-factory.RemoteConnectionFactory: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default.jms.connection-factory.RemoteConnectionFactory: WFLYMSGAMQ0028: Failed to create connection-factory > at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:67) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: ActiveMQIllegalStateException[errorType=ILLEGAL_STATE message=AMQ129005: Connector 'http-connector' not found on the main configuration file] > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1176) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.internalCreateCF(JMSServerManagerImpl.java:1138) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1400(JMSServerManagerImpl.java:103) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$5.runException(JMSServerManagerImpl.java:1007) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1494) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.createConnectionFactory(JMSServerManagerImpl.java:996) > at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:64) > ... 6 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4248) Add version 6 of the WildFly Elytron Subsystem Model / Schema

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4248: ---------------------------------------- Summary: Add version 6 of the WildFly Elytron Subsystem Model / Schema Key: WFCORE-4248 URL: https://issues.jboss.org/browse/WFCORE-4248 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11480) Possible to remove referenced activemq http-connector

by Marcel Šebek (Jira)

Marcel Šebek created WFLY-11480: ----------------------------------- Summary: Possible to remove referenced activemq http-connector Key: WFLY-11480 URL: https://issues.jboss.org/browse/WFLY-11480 Project: WildFly Issue Type: Bug Affects Versions: 15.0.0.Final Reporter: Marcel Šebek Assignee: Jason Greene It is possible to remove activemq http-connector that is referenced by broadcast-group, leading to crash on server next boot: 18:30:52,360 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 81) MSC000001: Failed to start service jboss.messaging-activemq.default.jms.connection-factory.RemoteConnectionFactory: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default.jms.connection-factory.RemoteConnectionFactory: WFLYMSGAMQ0028: Failed to create connection-factory at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:67) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: ActiveMQIllegalStateException[errorType=ILLEGAL_STATE message=AMQ129005: Connector 'http-connector' not found on the main configuration file] at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1176) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.internalCreateCF(JMSServerManagerImpl.java:1138) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.access$1400(JMSServerManagerImpl.java:103) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl$5.runException(JMSServerManagerImpl.java:1007) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1494) at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.createConnectionFactory(JMSServerManagerImpl.java:996) at org.wildfly.extension.messaging.activemq.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:64) ... 6 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2883) [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2883?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2883: -------------------------------------------- [~jomarko], The item "Navigate in results by tab" will be addressed by the https://issues.jboss.org/browse/DROOLS-3344; and the "Search is confirmed by enter" was removed because the search is invoked when the user types a new letter. > [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-2883 > URL: https://issues.jboss.org/browse/DROOLS-2883 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > h3. Acceptance test > - Find data type with > -- special characters > -- whitespaces > -- same text but different upper/lower case > - Search is cancelled by *escape* > - Search is confirmed by *enter* > - Navigate in results by *tab* (x) (https://issues.jboss.org/browse/DROOLS-3344) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2883) [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2883?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2883: --------------------------------------- Description: h3. Acceptance test - Find data type with -- special characters -- whitespaces -- same text but different upper/lower case - Search is cancelled by *escape* was: h3. Acceptance test - Find data type with -- special characters -- whitespaces -- same text but different upper/lower case - Search is cancelled by *escape* - Search is confirmed by *enter* - Navigate in results by *tab* (x) (https://issues.jboss.org/browse/DROOLS-3344) > [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-2883 > URL: https://issues.jboss.org/browse/DROOLS-2883 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > h3. Acceptance test > - Find data type with > -- special characters > -- whitespaces > -- same text but different upper/lower case > - Search is cancelled by *escape* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2883) [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-2883?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2883: --------------------------------------- Description: h3. Acceptance test - Find data type with -- special characters -- whitespaces -- same text but different upper/lower case - Search is cancelled by *escape* - Search is confirmed by *enter* - Navigate in results by *tab* (x) (https://issues.jboss.org/browse/DROOLS-3344) was: h3. Acceptance test - Find data type with -- special characters -- whitespaces -- same text but different upper/lower case - Search is cancelled by *escape* - Search is confirmed by *enter* - Navigate in results by *tab* > [DMN Designer] Add a Search bar in the Data Type dialog for search top level custom Data Types > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-2883 > URL: https://issues.jboss.org/browse/DROOLS-2883 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > h3. Acceptance test > - Find data type with > -- special characters > -- whitespaces > -- same text but different upper/lower case > - Search is cancelled by *escape* > - Search is confirmed by *enter* > - Navigate in results by *tab* (x) (https://issues.jboss.org/browse/DROOLS-3344) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools

by Christian Liebhardt (Jira)

Christian Liebhardt created DROOLS-3412: ------------------------------------------- Summary: Performance degradation with session pools Key: DROOLS-3412 URL: https://issues.jboss.org/browse/DROOLS-3412 Project: Drools Issue Type: Bug Reporter: Christian Liebhardt Assignee: Mario Fusco Hello, We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles). I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead. *What we did* # Create a session # Use the session # Dispose and reset the session and go back to 2 for the next facts *What happens with session pools* # Create a session # Use the session # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered. An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu... Thanks once more for your help. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3407) Need to use one rule in each one of the agendas efficiently in Kie Drools 7.12

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3407?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-3407. --------------------------------- Resolution: Explained I agree that the solution suggested by Edson should work. > Need to use one rule in each one of the agendas efficiently in Kie Drools 7.12 > ------------------------------------------------------------------------------ > > Key: DROOLS-3407 > URL: https://issues.jboss.org/browse/DROOLS-3407 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.12.0.Final > Reporter: Rafael Jordá > Assignee: Mario Fusco > Priority: Major > Labels: agenda, drools-tools, eclipse, rules > Fix For: 7.12.0.Final > > > Hi, I'm working in a project using Drools in Eclipse. I need to solve the following issue and I was wondering if you could help me. > I have a rule that needs to be triggered in each one of the agendas that I've defined in my drl file (it is a very important rule). > First, I tried not to set an agenda for that rule, but it only got executed at the end of the last agenda. > So the only thing that came to my mind was defining that rule in each one of the agendas, i.e., the same rule is repeated in all of them, which is not the most efficient solution. > Is this a normal issue? Is there a better solution? > Thanks. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-473) Run Kiali Python Client Tests Via Jenkins Job

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-473?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-473. -------------------------------- Resolution: Done Kiali-Python tests "test_api_methods.py" resides in kiali/tests/e2e, and thus no need for jenkins job specifically because they will be run thy the E2E job. > Run Kiali Python Client Tests Via Jenkins Job > --------------------------------------------- > > Key: SWSQE-473 > URL: https://issues.jboss.org/browse/SWSQE-473 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > Run tests via separate Jenkins job > Run tests via PR trigger -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2018