November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-33) Release Elytron Web 1.3.0.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-33?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELYWEB-33. ------------------------------ Resolution: Done > Release Elytron Web 1.3.0.Final > ------------------------------- > > Key: ELYWEB-33 > URL: https://issues.jboss.org/browse/ELYWEB-33 > Project: Elytron Web > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.3.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-490) b16 cluster is down

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-490?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-490: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > b16 cluster is down > ------------------- > > Key: SWSQE-490 > URL: https://issues.jboss.org/browse/SWSQE-490 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > B16 cluster is down / not working / broken. > Backgroud: > - Openshift projects were not deleting > - Restarted all (3) nodes > - Cluster did not come back up -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2769) callback methods for: before/after invoke BKM/DS

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-2769?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2769: ----------------------------------- Story Points: 3 > callback methods for: before/after invoke BKM/DS > ------------------------------------------------ > > Key: DROOLS-2769 > URL: https://issues.jboss.org/browse/DROOLS-2769 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > {quote}As part of another feature, I would like to create callback methods for both "before/after invoke BKM/DS", so that we can report on actual execution of BKMs and Decision Services. But this is a conversation for another day.{quote} > Ref https://github.com/kiegroup/drools/pull/1986#discussion_r204029977 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3068) DMN Compilation test e2e

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3068?page=com.atlassian.jira.plugi... ] Matteo Mortari resolved DROOLS-3068. ------------------------------------ Resolution: Done Epic status set as resolved as all linked JIRAs has been marked as resolved. > DMN Compilation test e2e > ------------------------ > > Key: DROOLS-3068 > URL: https://issues.jboss.org/browse/DROOLS-3068 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Follows-up on DROOLS-1701 to ensure DMN Compilation passes test in suites -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3308) DMN implement missing function

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3308: -------------------------------------- Summary: DMN implement missing function Key: DROOLS-3308 URL: https://issues.jboss.org/browse/DROOLS-3308 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFWIP-148?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFWIP-148: --------------------------------- Description: Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] {code} but newly it would have code AMQ219007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.] {code} This is problem for any user/customer who had monitoring based on those codes as this will require to change it. The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. was: Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] {code} but newly it would have code AMQ219007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] {code} This is problem for any user/customer who had monitoring based on those codes as this will require to change it. The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. > Artemis logging codes/IDs have changed for CORE protocol > -------------------------------------------------------- > > Key: WFWIP-148 > URL: https://issues.jboss.org/browse/WFWIP-148 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 > For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > {code} > but newly it would have code AMQ219007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.] > {code} > This is problem for any user/customer who had monitoring based on those codes as this will require to change it. > The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

by Miroslav Novak (Jira)

Miroslav Novak created WFWIP-148: ------------------------------------ Summary: Artemis logging codes/IDs have changed for CORE protocol Key: WFWIP-148 URL: https://issues.jboss.org/browse/WFWIP-148 Project: WildFly WIP Issue Type: Bug Components: Artemis Reporter: Miroslav Novak Assignee: Martyn Taylor Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] {code} but newly it would have code AMQ219007: {code} Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] {code} This is problem for any user/customer who had monitoring based on those codes as this will require to change it. The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3307) Make KnowledgePackage agnosting from Drools/jBPM

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3307: -------------------------------------- Summary: Make KnowledgePackage agnosting from Drools/jBPM Key: DROOLS-3307 URL: https://issues.jboss.org/browse/DROOLS-3307 Project: Drools Issue Type: Enhancement Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi current impl exposes both drools-specific and jbpm-specific methods core should not account for the underlying type: we'd rather give a wrapper or a common super-type instead of a different map for rules and processes. aim for API like: {code} kpg.get(Rules.class).getRules() {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3306) [DMN Designer] The output name is valorized for single output decision table

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3306: -------------------------------------- Summary: [DMN Designer] The output name is valorized for single output decision table Key: DROOLS-3306 URL: https://issues.jboss.org/browse/DROOLS-3306 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Matteo Mortari Assignee: Matteo Mortari h2. Manual acceptance test - Decision Table expression with single output, no name stored (/) - Decision Table expression with multiple outputs, name stored (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11320) Upgrade Infinispan to 9.4.1.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11320: ----------------------------------- Summary: Upgrade Infinispan to 9.4.1.Final Key: WFLY-11320 URL: https://issues.jboss.org/browse/WFLY-11320 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Release notes: https://issues.jboss.org/projects/ISPN/versions/12339377 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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