August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12358) Component upgrade of Narayana to 5.9.6.Final

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created WFLY-12358: --------------------------------------- Summary: Component upgrade of Narayana to 5.9.6.Final Key: WFLY-12358 URL: https://issues.jboss.org/browse/WFLY-12358 Project: WildFly Issue Type: Component Upgrade Components: Transactions Affects Versions: 17.0.1.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2362) Providing logical member name in JDBC_PING

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2362?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2362. ---------------------------- Resolution: Done Committed to {{master}} > Providing logical member name in JDBC_PING > ------------------------------------------ > > Key: JGRP-2362 > URL: https://issues.jboss.org/browse/JGRP-2362 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.17, 4.0.18, 4.0.19, 4.1.0, 4.0.20 > Reporter: S Pokutniy > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.3 > > > When using JDBC_PING and logical names instead of UUIDs and one of the cluster member crashes or get killed and this member is not coordinator then its database set still remains in the database as long as coordinator changes (independently from remove_old_coords_on_view_change /remove_all_data_on_view_change). If the the cluster is then restarted the old dataset makes connect() much slower (+30 seconds), as the members seem to be tryting to connect to it. Parameter remove_all_data_on_view_change seems to be the solution but it does not work as long as coordinator does not change, so practically the same as remove_old_coords_on_view_change. > The only solution seems to be to provide an appropriate delete statement in parameter initialize_sql, which would delete old entry, for example like this: delete from JGROUPSPING where ping_data like '%logical name%'. However, this is neither really quick nor the ideal solution, as ping_data's datatype is bytea or bit varying. > It would be great to have also logical name in JGROUPSPING, which is instead per default in insert(). This is also easy to implement as there is access to this information in PingData. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4416) ProjectClassLoader is no longer compatible with Wildfly modular ClassLoader

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4416?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4416. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/06a31bd9349487e64edb384875430df... > ProjectClassLoader is no longer compatible with Wildfly modular ClassLoader > --------------------------------------------------------------------------- > > Key: DROOLS-4416 > URL: https://issues.jboss.org/browse/DROOLS-4416 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > See https://github.com/wildfly-extras/wildfly-camel/issues/2831 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4416) ProjectClassLoader is no longer compatible with Wildfly modular ClassLoader

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4416?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4416: -------------------------------- Fix Version/s: 7.26.0.Final > ProjectClassLoader is no longer compatible with Wildfly modular ClassLoader > --------------------------------------------------------------------------- > > Key: DROOLS-4416 > URL: https://issues.jboss.org/browse/DROOLS-4416 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Fix For: 7.26.0.Final > > > See https://github.com/wildfly-extras/wildfly-camel/issues/2831 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4187) kie-dmn-validation: Incorrect import detection

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4187?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-4187 at 8/7/19 6:16 AM: ---------------------------------------------------------------- EDIT: I take it back, I misunderstood original comment here https://github.com/kiegroup/drools/commit/d057e0113c8e519a07554569f512045... and I was focusing on something else was (Author: tari_manga): I do not believe this comment: https://github.com/kiegroup/drools/commit/d057e0113c8e519a07554569f512045... is correct. Rules are V1x for latest version of the spec which Import uses "name" not the extended attribute. > kie-dmn-validation: Incorrect import detection > ---------------------------------------------- > > Key: DROOLS-4187 > URL: https://issues.jboss.org/browse/DROOLS-4187 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Matteo Mortari > Priority: Critical > Labels: rhpam74releasenote > Attachments: DROOLS-4187 > > > If I have a DMN file with {{Definitions}} attribute {{namespace}} and {{name}} both populated imported into another DMN file that does not use the {{drools:modelName}} extension in the {{Import}} node; validation of the imported model fails. > See https://github.com/kiegroup/drools/commit/d057e0113c8e519a07554569f512045... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Fix Version/s: (was: 18.0.0.Beta1) > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Tag/changelog > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2362) Providing logical member name in JDBC_PING

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2362?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2362: -------------------------------- OK, I changed the logic for handling view changes slightly: the coord now removes all data ({{remove_all_data_on_view_change == true}}) or only coord data ({{remove_all_data_on_view_change == true}}) regardless of whether the coordinator changed, or not. The second small change is that {{writeAll()}} only fetches data of non-removed members. This change will be in master pending a successful testsuite run. Try it out and let me know whether this works for you. > Providing logical member name in JDBC_PING > ------------------------------------------ > > Key: JGRP-2362 > URL: https://issues.jboss.org/browse/JGRP-2362 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.17, 4.0.18, 4.0.19, 4.1.0, 4.0.20 > Reporter: S Pokutniy > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.3 > > > When using JDBC_PING and logical names instead of UUIDs and one of the cluster member crashes or get killed and this member is not coordinator then its database set still remains in the database as long as coordinator changes (independently from remove_old_coords_on_view_change /remove_all_data_on_view_change). If the the cluster is then restarted the old dataset makes connect() much slower (+30 seconds), as the members seem to be tryting to connect to it. Parameter remove_all_data_on_view_change seems to be the solution but it does not work as long as coordinator does not change, so practically the same as remove_old_coords_on_view_change. > The only solution seems to be to provide an appropriate delete statement in parameter initialize_sql, which would delete old entry, for example like this: delete from JGROUPSPING where ping_data like '%logical name%'. However, this is neither really quick nor the ideal solution, as ping_data's datatype is bytea or bit varying. > It would be great to have also logical name in JGROUPSPING, which is instead per default in insert(). This is also easy to implement as there is access to this information in PingData. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12357) Upgrade Jackson2 databind to 2.9.9.3

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-12357: -------------------------------------- Summary: Upgrade Jackson2 databind to 2.9.9.3 Key: WFLY-12357 URL: https://issues.jboss.org/browse/WFLY-12357 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Martin Stefanko Fix For: 18.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12357) Upgrade Jackson2 databind to 2.9.9.3

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12357?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-12357: -------------------------------------- Assignee: Alessio Soldano (was: Martin Stefanko) > Upgrade Jackson2 databind to 2.9.9.3 > ------------------------------------ > > Key: WFLY-12357 > URL: https://issues.jboss.org/browse/WFLY-12357 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) DMN Editor/Test Scenarios design requirements (dev/UX)

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3126: --------------------------------------- [~uxdlc] I think some/most of the reported problems are still not solved so I think the epic cannot be closed > DMN Editor/Test Scenarios design requirements (dev/UX) > ------------------------------------------------------ > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam, drools-tools > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 August 2019