February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5991) [DMN Designer] Not able to open large dmn model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5991?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5991: -------------------------------- Steps to Reproduce: # Run the business central # Open a project # Import the asset [^big.dmn] Current: never ending loading screen appears !Screenshot from 2021-02-02 12-08-35.png|thumbnail! Expected: DMN model is successfully opened in reasonable time (seconds) was: # Run the business central # Open a project # Import the asset [^big.dmn] Current: never ending loading screen appears Expected: DMN model is successfully opened in reasonable time (seconds) > [DMN Designer] Not able to open large dmn model > ----------------------------------------------- > > Key: DROOLS-5991 > URL: https://issues.redhat.com/browse/DROOLS-5991 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.50.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: Screenshot from 2021-02-02 12-08-35.png, big.dmn > > > With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5991) [DMN Designer] Not able to open large dmn model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5991?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5991: -------------------------------- Attachment: Screenshot from 2021-02-02 12-08-35.png > [DMN Designer] Not able to open large dmn model > ----------------------------------------------- > > Key: DROOLS-5991 > URL: https://issues.redhat.com/browse/DROOLS-5991 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.50.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: Screenshot from 2021-02-02 12-08-35.png, big.dmn > > > With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5991) [DMN Designer] Not able to open large dmn model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5991?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5991: -------------------------------- Attachment: big.dmn > [DMN Designer] Not able to open large dmn model > ----------------------------------------------- > > Key: DROOLS-5991 > URL: https://issues.redhat.com/browse/DROOLS-5991 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.50.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > Attachments: big.dmn > > > With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5991) [DMN Designer] Not able to open large dmn model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5991?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5991: -------------------------------- Affects Version/s: 7.50.0.Final (was: 7.31.0.Final) > [DMN Designer] Not able to open large dmn model > ----------------------------------------------- > > Key: DROOLS-5991 > URL: https://issues.redhat.com/browse/DROOLS-5991 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.50.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Critical > Labels: drools-tools > > With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5991) [DMN Designer] Not able to open large dmn model

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5991: ----------------------------------- Summary: [DMN Designer] Not able to open large dmn model Key: DROOLS-5991 URL: https://issues.redhat.com/browse/DROOLS-5991 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.31.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes With the attached DMN model, user is unable to do changes and save them. -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13940) SingletonDeploymentJBossAllTestCase fails frequently in CI

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13940?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13940: ---------------------------------- Fix Version/s: 23.0.0.Beta1 > SingletonDeploymentJBossAllTestCase fails frequently in CI > ---------------------------------------------------------- > > Key: WFLY-13940 > URL: https://issues.redhat.com/browse/WFLY-13940 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 21.0.0.Beta1, 22.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 23.0.0.Beta1 > > > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13940) SingletonDeploymentJBossAllTestCase fails frequently in CI

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13940?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13940: ---------------------------------- Affects Version/s: 22.0.0.Final > SingletonDeploymentJBossAllTestCase fails frequently in CI > ---------------------------------------------------------- > > Key: WFLY-13940 > URL: https://issues.redhat.com/browse/WFLY-13940 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 21.0.0.Beta1, 22.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13940) SingletonDeploymentJBossAllTestCase fails frequently in CI

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13940?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13940: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/13628) > SingletonDeploymentJBossAllTestCase fails frequently in CI > ---------------------------------------------------------- > > Key: WFLY-13940 > URL: https://issues.redhat.com/browse/WFLY-13940 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 21.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2527) NPE if binding JGroups to an IP without interface

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2527?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2527. ---------------------------- Resolution: Done > NPE if binding JGroups to an IP without interface > ------------------------------------------------- > > Key: JGRP-2527 > URL: https://issues.redhat.com/browse/JGRP-2527 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.9 > Reporter: Pedro Ruivo > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.12, 5.1.5 > > > If you bind JGroups to 127.0.2.1 (or any IP without an interface, like 127.0.0.0/8 - loopback IP addresses (refers to self) RFC 5735), JGroups fails with an NPE: > {noformat} > Caused by: java.lang.NullPointerException > at org.jgroups.protocols.UDP.dumpSocketInfo(UDP.java:558) > at org.jgroups.protocols.UDP.createSockets(UDP.java:422) > at org.jgroups.protocols.UDP.start(UDP.java:292) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:868) > at org.jgroups.JChannel.startStack(JChannel.java:980) > at org.jgroups.JChannel._preConnect(JChannel.java:844) > at org.jgroups.JChannel.connect(JChannel.java:349) > at org.jgroups.JChannel.connect(JChannel.java:343) > {noformat} > The exception comes from this line: [https://github.com/belaban/JGroups/blob/4.x/src/org/jgroups/protocols/UDP...] > {{NetworkInterface.getByInetAddress(bind_addr)}} returns {{null}} since the IP does not have an interface. It would be nice to have a null check here to prevent the NPE. > This is useful for local testing when `port_range=0`. It allows having a dedicated IP for each JGroups instance. > Workaround: > The workaround requires you to create a virtual interface > {noformat} > sudo ifconfig lo:0 127.0.2.1 up > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2527) NPE if binding JGroups to an IP without interface

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2527?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2527: --------------------------- Fix Version/s: 5.1.5 4.2.12 > NPE if binding JGroups to an IP without interface > ------------------------------------------------- > > Key: JGRP-2527 > URL: https://issues.redhat.com/browse/JGRP-2527 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.9 > Reporter: Pedro Ruivo > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.12, 5.1.5 > > > If you bind JGroups to 127.0.2.1 (or any IP without an interface, like 127.0.0.0/8 - loopback IP addresses (refers to self) RFC 5735), JGroups fails with an NPE: > {noformat} > Caused by: java.lang.NullPointerException > at org.jgroups.protocols.UDP.dumpSocketInfo(UDP.java:558) > at org.jgroups.protocols.UDP.createSockets(UDP.java:422) > at org.jgroups.protocols.UDP.start(UDP.java:292) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:868) > at org.jgroups.JChannel.startStack(JChannel.java:980) > at org.jgroups.JChannel._preConnect(JChannel.java:844) > at org.jgroups.JChannel.connect(JChannel.java:349) > at org.jgroups.JChannel.connect(JChannel.java:343) > {noformat} > The exception comes from this line: [https://github.com/belaban/JGroups/blob/4.x/src/org/jgroups/protocols/UDP...] > {{NetworkInterface.getByInetAddress(bind_addr)}} returns {{null}} since the IP does not have an interface. It would be nice to have a null check here to prevent the NPE. > This is useful for local testing when `port_range=0`. It allows having a dedicated IP for each JGroups instance. > Workaround: > The workaround requires you to create a virtual interface > {noformat} > sudo ifconfig lo:0 127.0.2.1 up > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

4 years, 11 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 February 2021