July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4269?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4269: ----------------------------------- Sprint: 2019 Week 26-28 > kogito-codegen-tests: alternative testing strategy for codegen > -------------------------------------------------------------- > > Key: DROOLS-4269 > URL: https://issues.jboss.org/browse/DROOLS-4269 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, kogito, submarine > > Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin. > - create `kogito-codegen-tests` > - write data/rules/process sources under src/main/{java,resources} > - write tests under src/test/ > tests are now allowed to refer directly to codegenerated classes by name. > just use mvn compile test to run the tests > caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-4255: --------------------------------- Sprint: 2019 Week 26-28 > Add KIE server support for deploying custom Prometheus metrics > -------------------------------------------------------------- > > Key: DROOLS-4255 > URL: https://issues.jboss.org/browse/DROOLS-4255 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.24.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Labels: CustomerFocus > Fix For: 7.24.0.Final > > > The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-4255: --------------------------------- Labels: CustomerFocus (was: ) > Add KIE server support for deploying custom Prometheus metrics > -------------------------------------------------------------- > > Key: DROOLS-4255 > URL: https://issues.jboss.org/browse/DROOLS-4255 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.24.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Labels: CustomerFocus > Fix For: 7.24.0.Final > > > The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2726) Drools core doesn't run on AWS lambda

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2726?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2726. --------------------------------- Resolution: Explained As explained here https://stackoverflow.com/a/52691012/112779 the problem is caused by the fact that when you create a fat jar all kie.conf files must be concatenated in a single file. See https://docs.jboss.org/drools/release/7.22.0.Final/drools-docs/html_singl... to check how to do this. > Drools core doesn't run on AWS lambda > ------------------------------------- > > Key: DROOLS-2726 > URL: https://issues.jboss.org/browse/DROOLS-2726 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Adeela Huma > Assignee: Mario Fusco > Priority: Major > > When running drools on AWS lambda they get this exception apparently: > {code} > java.lang.ExceptionInInitializerError: > java.lang.ExceptionInInitializerError > java.lang.ExceptionInInitializerError > at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27) > ... > Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent > at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191) > at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97) > ... > {code} > Reporting the bug from stack overflow discussion: > https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2726) Drools core doesn't run on AWS lambda

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2726?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2726: -------------------------------- Sprint: 2019 Week 26-28 > Drools core doesn't run on AWS lambda > ------------------------------------- > > Key: DROOLS-2726 > URL: https://issues.jboss.org/browse/DROOLS-2726 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Adeela Huma > Assignee: Mario Fusco > Priority: Major > > When running drools on AWS lambda they get this exception apparently: > {code} > java.lang.ExceptionInInitializerError: > java.lang.ExceptionInInitializerError > java.lang.ExceptionInInitializerError > at org.kie.api.internal.utils.ServiceRegistry.getInstance(ServiceRegistry.java:27) > ... > Caused by: java.lang.RuntimeException: Child services [org.kie.api.internal.assembler.KieAssemblers] have no parent > at org.kie.api.internal.utils.ServiceDiscoveryImpl.buildMap(ServiceDiscoveryImpl.java:191) > at org.kie.api.internal.utils.ServiceDiscoveryImpl.getServices(ServiceDiscoveryImpl.java:97) > ... > {code} > Reporting the bug from stack overflow discussion: > https://stackoverflow.com/questions/51273121/optaplanner-with-aws-lambda -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2273) ASYM_ENCRYPT: deprecate encrypt_entire_message

by Dennis Reed (Jira)

[ https://issues.jboss.org/browse/JGRP-2273?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on JGRP-2273: ----------------------------------- SERIALIZE doesn't work with ASYM_ENCRYPT. Since it serializes the headers, they're no longer available to ASYM_ENCRYPT. But it depends on the headers (specifically from GMS) to function correctly. EncryptTest.testCapturingOfMessageByNonMemberAndResending() didn't detect this because it doesn't add SERIALIZE until after the cluster is already running (and ASYM_ENCRYPT has already intercepted those GMS messages). But if SERIALIZE is present before the channels start, the cluster is never able to form. That wasn't an issue with encrypt_entire_message because it checked those headers before serializing. Moving it to the separate SERIALIZE protocol is going to require some extra hacking to communicate that info between the two protocols. > ASYM_ENCRYPT: deprecate encrypt_entire_message > ---------------------------------------------- > > Key: JGRP-2273 > URL: https://issues.jboss.org/browse/JGRP-2273 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, {{encrypt_entire_message}} encrypts not only the payload, but also metadata such as destination and sender's address, headers and flags. > The rationale was to prevent replay attacks. However, this is not an issue, as replayed messages will simply get dropped by the retransmission layer (e.g. NAKACK2 or UNICAST3). > If people still want this feature, they can write a protocol _above_ {{ASYM_ENCRYPT}}, which serializes the entire message into the payload of a new message, and this would be exactly the same as setting {{encrypt_entire_message}} to {{true}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12262) Tasks-jsf quickstart has no pre-requisite of tasks quickstart

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12262?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12262: ----------------------------------- Description: The README.adoc of tasks-rf and tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. (was: The README.adoc of tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed.) > Tasks-jsf quickstart has no pre-requisite of tasks quickstart > ------------------------------------------------------------- > > Key: WFLY-12262 > URL: https://issues.jboss.org/browse/WFLY-12262 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > The README.adoc of tasks-rf and tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12262) Tasks-* quickstarts have no pre-requisite of tasks quickstart

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12262?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12262: ----------------------------------- Summary: Tasks-* quickstarts have no pre-requisite of tasks quickstart (was: Tasks-jsf quickstart has no pre-requisite of tasks quickstart) > Tasks-* quickstarts have no pre-requisite of tasks quickstart > ------------------------------------------------------------- > > Key: WFLY-12262 > URL: https://issues.jboss.org/browse/WFLY-12262 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > The README.adoc of tasks-rf and tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12262) Tasks-jsf quickstart has no pre-requisite of tasks quickstart

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12262?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12262: ----------------------------------- Summary: Tasks-jsf quickstart has no pre-requisite of tasks quickstart (was: Tasks-rf quickstart has no pre-requisite of tasks quickstart) > Tasks-jsf quickstart has no pre-requisite of tasks quickstart > ------------------------------------------------------------- > > Key: WFLY-12262 > URL: https://issues.jboss.org/browse/WFLY-12262 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > The README.adoc of tasks-rf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12262) Tasks-jsf quickstart has no pre-requisite of tasks quickstart

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12262?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12262: ----------------------------------- Description: The README.adoc of tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. (was: The README.adoc of tasks-rf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed.) > Tasks-jsf quickstart has no pre-requisite of tasks quickstart > ------------------------------------------------------------- > > Key: WFLY-12262 > URL: https://issues.jboss.org/browse/WFLY-12262 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 17.0.0.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > The README.adoc of tasks-jsf quickstart refers tasks QuickStart as pre-requisite, this is outdated and should be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 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 July 2019