November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3314) Add method to configure WorkItemManagerFactory programmatically

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3314?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3314: ----------------------------------- Sprint: 2018 Week 45-47 > Add method to configure WorkItemManagerFactory programmatically > --------------------------------------------------------------- > > Key: DROOLS-3314 > URL: https://issues.jboss.org/browse/DROOLS-3314 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Trivial > Labels: drools-core > > Currently only a property can be used. This JIRA is to track adding a simple setter to SessionConfiguration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3314) Add method to configure WorkItemManagerFactory programmatically

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3314?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3314: ----------------------------------- Story Points: 1 > Add method to configure WorkItemManagerFactory programmatically > --------------------------------------------------------------- > > Key: DROOLS-3314 > URL: https://issues.jboss.org/browse/DROOLS-3314 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Trivial > Labels: drools-core > > Currently only a property can be used. This JIRA is to track adding a simple setter to SessionConfiguration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3282) Should not move to next AgendaGroup even if current is empty

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3282?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3282: ----------------------------------- Sprint: 2018 Week 45-47 > Should not move to next AgendaGroup even if current is empty > ------------------------------------------------------------ > > Key: DROOLS-3282 > URL: https://issues.jboss.org/browse/DROOLS-3282 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current implementation moves to next agend group if current agenda group is empty. This is unexpected, and in part detrimental in the impl of units: it is not possible to suspend execution of rules by switching to an empty group, because the engine will move to the next group anyway: > {code} > return nextRule != null && (!ruleAgendaItem.getAgendaGroup().equals( nextRule.getAgendaGroup() ) || !isHigherSalience(nextRule)); > {code} > because the change in behavior is potentially backwards incompatible we add a flag {{keepWhenEmpty}} that must be set to {{true}} when we want to enable this new behavior -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11377) messaging-clustering-singleton does not run under OpenShift

by Robert Baumgartner (Jira)

[ https://issues.jboss.org/browse/WFLY-11377?page=com.atlassian.jira.plugin... ] Robert Baumgartner edited comment on WFLY-11377 at 11/19/18 10:41 AM: ---------------------------------------------------------------------- messaging-clustering-singleton needs some update before it can run under OpenShift. The postconfigure.sh will be executed automatically after the container will be started. please add the attached two files to the project. extensions/extensions.cli extensions/postconfigure.sh was (Author: rbaumgar): messaging-clustering-singleton needs some update before it can run under OpenShift. The postconfigure.sh will be executed automatically after the container will be started. please add following two files: extensions/extensions.cli ##Batch file to configure the standalone server for the messaging-clustering-singleton quickstart. embed-server --server-config=standalone-openshift.xml batch # -- The console is disabled by default in the Full HA profile. Enable the console to allow us to view the quickstart output. # /subsystem=logging/console-handler=CONSOLE:add(level=INFO,formatter="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n") # /subsystem=logging/root-logger=ROOT:add-handler(name="CONSOLE") # -- Enable clustering, and set a cluster password /subsystem=messaging-activemq/server=default:write-attribute(name=cluster-password, value=password) # -- Add mdb-delivery-group named "my-mdb-delivery-group" /subsystem=ejb3/mdb-delivery-group=my-mdb-delivery-group:add(active=true) # -- Deploy the messaging-clustering-singleton.war file # deploy /deployments/messaging-clustering-singleton.war # -- Run this batch file run-batch # Reload the server reload extensions/postconfigure.sh #!/bin/bash echo " " echo " $0 start" echo " " ${JBOSS_HOME}/bin/jboss-cli.sh --file=${JBOSS_HOME}/extensions/extensions.cli echo " " echo " $1 end" echo " " > messaging-clustering-singleton does not run under OpenShift > ----------------------------------------------------------- > > Key: WFLY-11377 > URL: https://issues.jboss.org/browse/WFLY-11377 > Project: WildFly > Issue Type: Enhancement > Environment: JBoss EAP 7.1 and OpenShift 3.11 > Reporter: Robert Baumgartner > Assignee: Jason Greene > Priority: Major > Attachments: extensions.cli, postconfigure.sh > > > create a project in OpenShift > create a new a app with the quickstart: messaging-clustering-singleton > install-singleton is not executed... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3328) PhreakAsyncSendNode triggers service discovery even when it's not used

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3328?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3328: ----------------------------------- Story Points: 1 > PhreakAsyncSendNode triggers service discovery even when it's not used > ---------------------------------------------------------------------- > > Key: DROOLS-3328 > URL: https://issues.jboss.org/browse/DROOLS-3328 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > I am investigating ways to startup a stripped down version of the rule engine. > in 7.8.0 the following snippet did _not_ trigger service discovery : > {code} > CanonicalKiePackages packages = new MyKiePackagesBuilder(model, ProjectClassLoader.createProjectClassLoader()).build(); > InternalKnowledgeBase kBase = new KnowledgeBaseImpl("defaultname", null); > kBase.addPackages(packages.getKiePackages()); > kieSession = kBase.newKieSession(); > {code} > this is because no call to {{ExecutorProviderFactory.getExecutorProvider()}} occurs anywhere. However in a recent release, {{PhreakAsyncSendNode}} invokes this method, while initializing a static field > {code} > private static final Executor executor = ExecutorProviderFactory.getExecutorProvider().getExecutor(); > {code} > This triggers a *full service discovery* which loads a bunch of other unrelated services. > Solution: avoid service discovery in that class, or delegate to a method (the service utility caches that field anyway, so it's not necessary to set a static field there) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3328) PhreakAsyncSendNode triggers service discovery even when it's not used

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3328?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3328: ----------------------------------- Sprint: 2018 Week 45-47 > PhreakAsyncSendNode triggers service discovery even when it's not used > ---------------------------------------------------------------------- > > Key: DROOLS-3328 > URL: https://issues.jboss.org/browse/DROOLS-3328 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > I am investigating ways to startup a stripped down version of the rule engine. > in 7.8.0 the following snippet did _not_ trigger service discovery : > {code} > CanonicalKiePackages packages = new MyKiePackagesBuilder(model, ProjectClassLoader.createProjectClassLoader()).build(); > InternalKnowledgeBase kBase = new KnowledgeBaseImpl("defaultname", null); > kBase.addPackages(packages.getKiePackages()); > kieSession = kBase.newKieSession(); > {code} > this is because no call to {{ExecutorProviderFactory.getExecutorProvider()}} occurs anywhere. However in a recent release, {{PhreakAsyncSendNode}} invokes this method, while initializing a static field > {code} > private static final Executor executor = ExecutorProviderFactory.getExecutorProvider().getExecutor(); > {code} > This triggers a *full service discovery* which loads a bunch of other unrelated services. > Solution: avoid service discovery in that class, or delegate to a method (the service utility caches that field anyway, so it's not necessary to set a static field there) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11377) messaging-clustering-singleton does not run under OpenShift

by Robert Baumgartner (Jira)

[ https://issues.jboss.org/browse/WFLY-11377?page=com.atlassian.jira.plugin... ] Robert Baumgartner updated WFLY-11377: -------------------------------------- Attachment: extensions.cli postconfigure.sh > messaging-clustering-singleton does not run under OpenShift > ----------------------------------------------------------- > > Key: WFLY-11377 > URL: https://issues.jboss.org/browse/WFLY-11377 > Project: WildFly > Issue Type: Enhancement > Environment: JBoss EAP 7.1 and OpenShift 3.11 > Reporter: Robert Baumgartner > Assignee: Jason Greene > Priority: Major > Attachments: extensions.cli, postconfigure.sh > > > create a project in OpenShift > create a new a app with the quickstart: messaging-clustering-singleton > install-singleton is not executed... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-2924: ----------------------------------- Sprint: 2018 Week 33-35, 2018 Week 42-44 (was: 2018 Week 33-35, 2018 Week 42-44, 2018 Week 45-47) > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: Stunner, drools-core, ruleunits > > The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g. > - rule units (Drools) > - process units (jBPM) > - etc. > then the mechanism must allow for extensions. > This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11377) messaging-clustering-singleton does not run under OpenShift

by Robert Baumgartner (Jira)

[ https://issues.jboss.org/browse/WFLY-11377?page=com.atlassian.jira.plugin... ] Robert Baumgartner edited comment on WFLY-11377 at 11/19/18 10:38 AM: ---------------------------------------------------------------------- messaging-clustering-singleton needs some update before it can run under OpenShift. The postconfigure.sh will be executed automatically after the container will be started. please add following two files: extensions/extensions.cli ##Batch file to configure the standalone server for the messaging-clustering-singleton quickstart. embed-server --server-config=standalone-openshift.xml batch # -- The console is disabled by default in the Full HA profile. Enable the console to allow us to view the quickstart output. # /subsystem=logging/console-handler=CONSOLE:add(level=INFO,formatter="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n") # /subsystem=logging/root-logger=ROOT:add-handler(name="CONSOLE") # -- Enable clustering, and set a cluster password /subsystem=messaging-activemq/server=default:write-attribute(name=cluster-password, value=password) # -- Add mdb-delivery-group named "my-mdb-delivery-group" /subsystem=ejb3/mdb-delivery-group=my-mdb-delivery-group:add(active=true) # -- Deploy the messaging-clustering-singleton.war file # deploy /deployments/messaging-clustering-singleton.war # -- Run this batch file run-batch # Reload the server reload extensions/postconfigure.sh #!/bin/bash echo " " echo " $0 start" echo " " ${JBOSS_HOME}/bin/jboss-cli.sh --file=${JBOSS_HOME}/extensions/extensions.cli echo " " echo " $1 end" echo " " was (Author: rbaumgar): messaging-clustering-singleton needs some update before it can run under OpenShift. The postconfigure.sh will be executed automatically after the container will be started. please add following two files: extensions/extensions.cli ##Batch file to configure the standalone server for the messaging-clustering-singleton quickstart. embed-server --server-config=standalone-openshift.xml batch # -- The console is disabled by default in the Full HA profile. Enable the console to allow us to view the quickstart output. # /subsystem=logging/console-handler=CONSOLE:add(level=INFO,formatter="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n") # /subsystem=logging/root-logger=ROOT:add-handler(name="CONSOLE") # -- Enable clustering, and set a cluster password /subsystem=messaging-activemq/server=default:write-attribute(name=cluster-password, value=password) # -- Add mdb-delivery-group named "my-mdb-delivery-group" /subsystem=ejb3/mdb-delivery-group=my-mdb-delivery-group:add(active=true) # -- Deploy the messaging-clustering-singleton.war file # deploy /deployments/messaging-clustering-singleton.war # -- Run this batch file run-batch # Reload the server reload extensions/postconfigure.sh #!/bin/bash echo " " echo " $0 start" echo " " ${JBOSS_HOME}/bin/jboss-cli.sh --file=${JBOSS_HOME}/extensions/extensions.cli echo " " echo " $1 end" echo " " > messaging-clustering-singleton does not run under OpenShift > ----------------------------------------------------------- > > Key: WFLY-11377 > URL: https://issues.jboss.org/browse/WFLY-11377 > Project: WildFly > Issue Type: Enhancement > Environment: JBoss EAP 7.1 and OpenShift 3.11 > Reporter: Robert Baumgartner > Assignee: Jason Greene > Priority: Major > > create a project in OpenShift > create a new a app with the quickstart: messaging-clustering-singleton > install-singleton is not executed... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11377) messaging-clustering-singleton does not run under OpenShift

by Robert Baumgartner (Jira)

[ https://issues.jboss.org/browse/WFLY-11377?page=com.atlassian.jira.plugin... ] Robert Baumgartner commented on WFLY-11377: ------------------------------------------- messaging-clustering-singleton needs some update before it can run under OpenShift. The postconfigure.sh will be executed automatically after the container will be started. please add following two files: extensions/extensions.cli ##Batch file to configure the standalone server for the messaging-clustering-singleton quickstart. embed-server --server-config=standalone-openshift.xml batch # -- The console is disabled by default in the Full HA profile. Enable the console to allow us to view the quickstart output. # /subsystem=logging/console-handler=CONSOLE:add(level=INFO,formatter="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n") # /subsystem=logging/root-logger=ROOT:add-handler(name="CONSOLE") # -- Enable clustering, and set a cluster password /subsystem=messaging-activemq/server=default:write-attribute(name=cluster-password, value=password) # -- Add mdb-delivery-group named "my-mdb-delivery-group" /subsystem=ejb3/mdb-delivery-group=my-mdb-delivery-group:add(active=true) # -- Deploy the messaging-clustering-singleton.war file # deploy /deployments/messaging-clustering-singleton.war # -- Run this batch file run-batch # Reload the server reload extensions/postconfigure.sh #!/bin/bash echo " " echo " $0 start" echo " " ${JBOSS_HOME}/bin/jboss-cli.sh --file=${JBOSS_HOME}/extensions/extensions.cli echo " " echo " $1 end" echo " " > messaging-clustering-singleton does not run under OpenShift > ----------------------------------------------------------- > > Key: WFLY-11377 > URL: https://issues.jboss.org/browse/WFLY-11377 > Project: WildFly > Issue Type: Enhancement > Environment: JBoss EAP 7.1 and OpenShift 3.11 > Reporter: Robert Baumgartner > Assignee: Jason Greene > Priority: Major > > create a project in OpenShift > create a new a app with the quickstart: messaging-clustering-singleton > install-singleton is not executed... -- This message was sent by Atlassian Jira (v7.12.1#712002)

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