April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2403. ---------------------------- Resolution: Done Thread dumps are done only *once*: when the pool is full for the first time. Once {{thread_dump}} is reset, next time around another thread dump will be logged at FATAL level. To enable the next thread dump: {{probe.sh op=TP.resetThreadDump}} > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > The question is *when* do we do this? If the pool fluctuates between almost-full and full, we can't obviously take a thread dump every time! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3200) [DMN Designer] Properties Panel Hints

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3200?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-3200. ------------------------------- Resolution: Won't Fix > [DMN Designer] Properties Panel Hints > ------------------------------------- > > Key: DROOLS-3200 > URL: https://issues.redhat.com/browse/DROOLS-3200 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Following DROOLS-3145 we need to identify most important fields set via properties panel and provide hints directly in the properties panel to support self-documentary product effort. > The hints should shortly explain the fields and provide sample valid values if applicable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1971) [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1971?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1971. ------------------------------- Resolution: Won't Do No input for 3 years > [DMN Editor] Change DirectionalLine to extend AbstractOffsetMultiPointShape > --------------------------------------------------------------------------- > > Key: DROOLS-1971 > URL: https://issues.redhat.com/browse/DROOLS-1971 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > See:- > 1) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 2) https://github.com/manstis/kie-wb-common/commit/bde36c9a2f5b56d1adb13015c... > 3) <conan> manstis you want to extend {{AbstractOffsetMultiPointShape}} not {{AbstractDirectionalMultiPointShape}} as {{AbstractDirectionalMultiPointShape}} has 3 attributes, only applicable to orthogonal lines. you have neither a direction nor a direction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4329) [DMN Editor] Move UberElement to UberElemental in popup

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4329?page=com.atlassian.jira.plug... ] Jozef Marko reassigned DROOLS-4329: ----------------------------------- Assignee: Jozef Marko (was: Michael Anstis) > [DMN Editor] Move UberElement to UberElemental in popup > ------------------------------------------------------- > > Key: DROOLS-4329 > URL: https://issues.redhat.com/browse/DROOLS-4329 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Jozef Marko > Priority: Major > > AbstractPopoverViewImpl current uses deprecated UberElement, which forces all popups to use deprecated classes. It have to be migrated to UberElemental. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3614: -------------------------------- Priority: Optional (was: Major) > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final, 7.36.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Optional > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3614: -------------------------------- Tester: Jozef Marko > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final, 7.36.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3614: -------------------------------- Affects Version/s: 7.36.0.Final > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final, 7.36.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2657) [DMN Designer] Select Box for Decision Table input columns

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-2657?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-2657. ------------------------------- Fix Version/s: 7.36.0.Final Resolution: Won't Do No input for ~2 years. Reported internally. If customer requires can report with proper description/versions. > [DMN Designer] Select Box for Decision Table input columns > ---------------------------------------------------------- > > Key: DROOLS-2657 > URL: https://issues.redhat.com/browse/DROOLS-2657 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Fix For: 7.36.0.Final > > > Currently the decision table input columns can be named with any name. However their names should correspond to InputData elements in the DRG, thus we should provide select box for each decision table input column, where user would select corresponding InputData element for the given decision table input column. > h3. Acceptance test > # Sorting in select box > # Rename InputData, change reflected in select box > # Same InputData connected to multiple nodes, appropriate select boxes contain the value -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3317?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-3317. ------------------------------- Fix Version/s: 7.36.0.Final Resolution: Cannot Reproduce Tried to construct rule with setting boolean on right site. No validation/build error thrown. > Guided Decision Tables: Insert in RHS not creating valid code for boolean fields. > --------------------------------------------------------------------------------- > > Key: DROOLS-3317 > URL: https://issues.redhat.com/browse/DROOLS-3317 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.15.0.Final > Reporter: Toni Rikkola > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Fix For: 7.36.0.Final > > > Insert a fact with a boolean field in dtable RHS. > The DRL generated looks like this: > {code:java} > rule "Row 3 The Table" > dialect "mvel" > when > s : Source( age >= 18 , kitten == "Dog" ) > then > s.setRisk( "ok" ); > DroolsUtil fact0 = new DroolsUtil(); > fact0.setARuleFired( true ); > insert( fact0 ); > end > {code} > The line > {code:java} > fact0.setARuleFired( true ); > {code} > does not compile. It should be ( for example ): > {code:java} > fact0.aRuleFired = true; > {code} > The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2464) Getting OutOfMemory Error

by Bhavesh Kharwa (Jira)

Bhavesh Kharwa created JGRP-2464: ------------------------------------ Summary: Getting OutOfMemory Error Key: JGRP-2464 URL: https://issues.redhat.com/browse/JGRP-2464 Project: JGroups Issue Type: Bug Affects Versions: 3.6.13 Reporter: Bhavesh Kharwa Assignee: Bela Ban Attachments: oom-jgroup.jpg I am using artemis version 2.11.0 and run artemis in master slave. There are two master and each master having slave. Please find attached screenshot of OutOfMemory error. I have tried to reproduce this issue but not able to reproduce it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 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 April 2020