July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4237) Consume Drools output using an API

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4237?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4237. ---------------------------------------- Resolution: Done > Consume Drools output using an API > ---------------------------------- > > Key: DROOLS-4237 > URL: https://issues.jboss.org/browse/DROOLS-4237 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4241) Prototype concurrent rule units

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4241?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-4241: ----------------------------------- Assignee: Mario Fusco (was: Edoardo Vacchi) > Prototype concurrent rule units > ------------------------------- > > Key: DROOLS-4241 > URL: https://issues.jboss.org/browse/DROOLS-4241 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Mario Fusco > Priority: Major > Labels: drools-core, kogito, submarine > Fix For: 8.0.0.Final > > > follow up to DROOLS-3819 > Prototype for concurrent executor for units > *deliverable* a code example -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12226: --------------------------------------- Assignee: Brian Stansberry (was: Emmanuel Hugonnet) Resolution: Done I'm resolving this as we've worked around it. The Artemis issue tracks the real fix. > IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12226 > URL: https://issues.jboss.org/browse/WFLY-12226 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 18.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Brian Stansberry > Priority: Critical > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > There is a warning during start with standalone-full*.xml: > {noformat} > 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA > 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra > 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started > 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory > {noformat} > For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11106) Kabir Test(For demo)

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11106?page=com.atlassian.jira.plugin... ] Kabir Khan deleted WFLY-11106: ------------------------------ > Kabir Test(For demo) > -------------------- > > Key: WFLY-11106 > URL: https://issues.jboss.org/browse/WFLY-11106 > Project: WildFly > Issue Type: Feature Request > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > Labels: EAP-CD15, EAP-CD16, EAP-CD17 > > An issue for me to move around the board to test the tooling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-804) Kiali Release Notifier Jenkins Job Is Broken

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-804?page=com.atlassian.jira.plugin.... ] Matthew Mahoney commented on SWSQE-804: --------------------------------------- Fixed job to use quay.io repo and tag > Kiali Release Notifier Jenkins Job Is Broken > -------------------------------------------- > > Key: SWSQE-804 > URL: https://issues.jboss.org/browse/SWSQE-804 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > kiali-release-notifier is using the incorrect container repo (should be using quay.io. and not docker.io). Also, the Kiali version / tag is in correct. > Reference job: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/kiali-workflow/j... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-804) Kiali Release Notifier Jenkins Job Is Broken

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-804?page=com.atlassian.jira.plugin.... ] Matthew Mahoney resolved SWSQE-804. ----------------------------------- Resolution: Done > Kiali Release Notifier Jenkins Job Is Broken > -------------------------------------------- > > Key: SWSQE-804 > URL: https://issues.jboss.org/browse/SWSQE-804 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > kiali-release-notifier is using the incorrect container repo (should be using quay.io. and not docker.io). Also, the Kiali version / tag is in correct. > Reference job: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/kiali-workflow/j... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4237) Consume Drools output using an API

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4237?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4237: --------------------------------------- Sprint: 2019 Week 26-28 (was: 2019 Week 29-31) > Consume Drools output using an API > ---------------------------------- > > Key: DROOLS-4237 > URL: https://issues.jboss.org/browse/DROOLS-4237 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4236) Testing of the HACEP

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4236?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4236: --------------------------------------- Sprint: 2019 Week 26-28 (was: 2019 Week 29-31) > Testing of the HACEP > --------------------- > > Key: DROOLS-4236 > URL: https://issues.jboss.org/browse/DROOLS-4236 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4275) Drools-wb webapp does not start

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4275: ---------------------------------------- Summary: Drools-wb webapp does not start Key: DROOLS-4275 URL: https://issues.jboss.org/browse/DROOLS-4275 Project: Drools Issue Type: Bug Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Drools-wb webapp jboss does not start due to ambiguous dependencies at WELD -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4161: --------------------------------------- [~kkufova] It might be not that simple because we discussed about create a template tight to a decision service (= keep as EXPECT only decision in the decision service and as GIVEN all and only the needed inputs) so if we change the name of the decision service to invoke I expect the template to be updated (or at least it should be nice to have) And what about revert to the full model testing? Should we support this too? Btw we can just change the name in the panel as first step of course > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019