October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3093) Necessary configuration information is missing when running rules engine in active mode

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3093?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3093: -------------------------------- Fix Version/s: 7.13.0.Final > Necessary configuration information is missing when running rules engine in active mode > --------------------------------------------------------------------------------------- > > Key: DROOLS-3093 > URL: https://issues.jboss.org/browse/DROOLS-3093 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.12.0.Final > Reporter: Lyle Wang > Assignee: Mario Fusco > Priority: Major > Fix For: 7.13.0.Final > > > When following this doc page to run rules engine in active mode > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... > If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. > https://access.redhat.com/solutions/3645752 > Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: > ------------------------------------------------------------- > KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.ok ); > KieSession ksession = kContainer.newKieSession("ksession-name", kconf); > ------------------------------------------------------------- > Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : > https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3093) Necessary configuration information is missing when running rules engine in active mode

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3093?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3093: -------------------------------- Description: When following this doc page to run rules engine in active mode https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. https://access.redhat.com/solutions/3645752 Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: ------------------------------------------------------------- KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.ok ); KieSession ksession = kContainer.newKieSession("ksession-name", kconf); ------------------------------------------------------------- Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... was: When following this doc page to run rules engine in active mode https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. https://access.redhat.com/solutions/3645752 Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: ------------------------------------------------------------- KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.THREAD_SAFE_TRACKABLE ); KieSession ksession = kContainer.newKieSession("ksession-name", kconf); ------------------------------------------------------------- Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... > Necessary configuration information is missing when running rules engine in active mode > --------------------------------------------------------------------------------------- > > Key: DROOLS-3093 > URL: https://issues.jboss.org/browse/DROOLS-3093 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.12.0.Final > Reporter: Lyle Wang > Assignee: Mario Fusco > Priority: Major > > When following this doc page to run rules engine in active mode > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... > If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. > https://access.redhat.com/solutions/3645752 > Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: > ------------------------------------------------------------- > KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.ok ); > KieSession ksession = kContainer.newKieSession("ksession-name", kconf); > ------------------------------------------------------------- > Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : > https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3093) Necessary configuration information is missing when running rules engine in active mode

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3093?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-3093. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/kie-docs/commit/d66f5102cf31181e23b2cd145725c... > Necessary configuration information is missing when running rules engine in active mode > --------------------------------------------------------------------------------------- > > Key: DROOLS-3093 > URL: https://issues.jboss.org/browse/DROOLS-3093 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.12.0.Final > Reporter: Lyle Wang > Assignee: Mario Fusco > Priority: Major > > When following this doc page to run rules engine in active mode > https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html/ch07.h... > If application code opens another thread and do ksession.insert(fact) then it's possible to have threading issues. > https://access.redhat.com/solutions/3645752 > Requesting to add suggestion to highlight "ThreadSafeTrackableTimeJobFactoryManager" should be used in multithreading environment, code example: > ------------------------------------------------------------- > KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.ok ); > KieSession ksession = kContainer.newKieSession("ksession-name", kconf); > ------------------------------------------------------------- > Following code change has been made to update the default implementation to use ThreadSafeTrackableTimeJobFactoryManager : > https://github.com/kiegroup/drools/commit/92623e2435401db4f80eaf5e3e804c1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-406) Deprecate ReplicationConfig and remove from next schema version

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/JBMETA-406?page=com.atlassian.jira.plugin... ] Paul Ferraro updated JBMETA-406: -------------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/132 (was: https://github.com/jboss/metadata/pull/120) > Deprecate ReplicationConfig and remove from next schema version > --------------------------------------------------------------- > > Key: JBMETA-406 > URL: https://issues.jboss.org/browse/JBMETA-406 > Project: JBoss Metadata > Issue Type: Task > Components: web > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > This configuration is planning to grow in complexity and is moving into a WildFly subsystem. > See: https://issues.jboss.org/browse/WFLY-5550 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-3067: ------------------------------------------------ Thank you, [~jomarko]. Your description is good enough. > [DMN Designer] Automatic Layout Feature Workbench Integration > ------------------------------------------------------------- > > Key: DROOLS-3067 > URL: https://issues.jboss.org/browse/DROOLS-3067 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-10-10 08-22-25.png, a3.dmn, auto.png, manual.png > > > Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature. > h2. Acceptance tests > # -User is prompted if he wants or not to apply autolayout feature- discussed in comments > # Positioning is automatically stored after model opening (/) > # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/) > # Tree, top node in the middle of the screen, some branches to all sides (/) > # Graph with big crossing of edges, similar to complete graph (/) > # Large (but sparse) graph, not all nodes visible without scrolling (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3032: ------------------------------------- [~uxdlc] I am completely satisfied with this last one. Totally self-explanatory, self-documented from my point of view. However lets wait for opinions of other involved people. > [DMN Designer] UX "empty" state for custom data types > ----------------------------------------------------- > > Key: DROOLS-3032 > URL: https://issues.jboss.org/browse/DROOLS-3032 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screen Shot 2018-10-11 at 12.01.44 PM.png, Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3032: -------------------------------- Attachment: Screen Shot 2018-10-11 at 12.01.44 PM.png > [DMN Designer] UX "empty" state for custom data types > ----------------------------------------------------- > > Key: DROOLS-3032 > URL: https://issues.jboss.org/browse/DROOLS-3032 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screen Shot 2018-10-11 at 12.01.44 PM.png, Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3032: ------------------------------------- [~jomarko] We could use the pattern verbatim, but then might need to hide the other Add button (like so), wdyt? !Screen Shot 2018-10-11 at 12.01.44 PM.png|thumbnail! > [DMN Designer] UX "empty" state for custom data types > ----------------------------------------------------- > > Key: DROOLS-3032 > URL: https://issues.jboss.org/browse/DROOLS-3032 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-10-11 at 10.56.18 AM.png, Screen Shot 2018-10-11 at 12.01.44 PM.png, Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11084) inter-app quickstart does not deploy (WildFly 14.0.1)

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11084?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11084: ----------------------------------------- Unless having the circular dependency is somehow critical to what the QS is demonstrating, it could be reworked to not have that. Don't have appA depend on appB. If demonstrating more than one inter-app dependency is wanted, introduce an appC. > inter-app quickstart does not deploy (WildFly 14.0.1) > ----------------------------------------------------- > > Key: WFLY-11084 > URL: https://issues.jboss.org/browse/WFLY-11084 > Project: WildFly > Issue Type: Bug > Reporter: Kevin Eagles > Assignee: Bartosz Baranowski > Priority: Critical > > Using Wildfly 14.0.1.Final > When deploying inter-app-appA.war, Wildfly complains about the EJB lookup for: > @ejb(lookup = "java:global/inter-app-appB/BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar") > Likewise, when deploying inter-app-appB.war, Wildfly complains about the EJB lookup for: > @ejb(lookup = "java:global/inter-app-appA/FooImpl!org.jboss.as.quickstarts.interapp.shared.Foo") > To reproduce, from the inter-app quickstart: > mvn install wildfly:deploy > Can also reproduce by just doing an mvn install, then manually deploying the jar, then appA, then appB using the HAL Management Console. > {noformat} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] > } > 09:56:51,014 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"] > } > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2684) Highlight test result in the grid

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-2684?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2684: ---------------------------------- Issue Type: Story (was: Task) > Highlight test result in the grid > --------------------------------- > > Key: DROOLS-2684 > URL: https://issues.jboss.org/browse/DROOLS-2684 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > Priority: Major > > As user I want to see errors of test run directly in the grid -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018