January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-2217: -------------------------------------- Assignee: Michael Anstis (was: Matteo Mortari) > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2217: -------------------------------- Steps to Reproduce: # Create new DMN diagram # Add Decision node # Open Decision node properties # Configure this Decision node as Context Entry ## !Screenshot from 2018-01-22 14-01-38.png|thumbnail! # Save DMN diagram # Check server log, there will be: [^error.log] # Reopen the DMN Diagram # Check the Decision node properties # The Decision node won't be configured as a Context Entry more Please notice that the issue is not reproducible if you use context entry shown as below: !Screenshot from 2018-01-22 14-02-13.png|thumbnail! was: # Create new DMN diagram # Add Decision node # Open Decision node properties # Configure this Decision node as Context Entry # Save DMN diagram # Check server log, there will be: [^error.log] # Reopen the DMN Diagram # Check the Decision node properties # The Decision node won't be configured as a Context Entry more > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2247) RPC does not invoke interface's default methods inherited

by rokk ebol (JIRA)

rokk ebol created JGRP-2247: ------------------------------- Summary: RPC does not invoke interface's default methods inherited Key: JGRP-2247 URL: https://issues.jboss.org/browse/JGRP-2247 Project: JGroups Issue Type: Feature Request Affects Versions: 4.0.8 Environment: jgroups 4.0.8.Final java version "1.8.0_151" Java(TM) SE Runtime Environment (build 1.8.0_151-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode) on win 10 Reporter: rokk ebol Assignee: Bela Ban org.jgroups.blocks.MethodCall#getAllMethods looks for methods up there in superclasses but not in interfaces, which can contain default methods since java 8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2217: -------------------------------- Attachment: Screenshot from 2018-01-22 14-02-13.png Screenshot from 2018-01-22 14-01-38.png > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1492) java.nio.file.InvalidPathException: Illegal char ':' at krb5.conf

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1492?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1492: ------------------------------- Assignee: Jan Kalina > java.nio.file.InvalidPathException: Illegal char ':' at krb5.conf > ----------------------------------------------------------------- > > Key: ELY-1492 > URL: https://issues.jboss.org/browse/ELY-1492 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.2.0.Beta11 > Reporter: Martin Choma > Assignee: Jan Kalina > > This occures in TS on JDK9 on Windows in tests: > * org.wildfly.security.sasl.gssapi.CommunicationSuiteChild > * org.wildfly.security.sasl.gs2.Gs2SuiteChild > {noformat} > javax.security.auth.login.LoginException: > java.nio.file.InvalidPathException: Illegal char <:> at index 2: /W:/workspace/wildfly-elytron-unit-tests/4ad7c91f/wildfly-elytron/target/test-classes/krb5.conf > at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) > at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) > at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) > at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92) > at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:229) > at java.base/java.nio.file.Paths.get(Paths.java:84) > at java.security.jgss/sun.security.krb5.Config.lambda$loadConfigFile$0(Config.java:639) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/java.security.AccessController.doPrivileged(AccessController.java:429) > at java.security.jgss/sun.security.krb5.Config.loadConfigFile(Config.java:638) > at java.security.jgss/sun.security.krb5.Config.<init>(Config.java:176) > at java.security.jgss/sun.security.krb5.Config.refresh(Config.java:115) > at jdk.security.auth/com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:528) > at java.base/javax.security.auth.login.LoginContext.invoke(LoginContext.java:726) > at java.base/javax.security.auth.login.LoginContext.access$000(LoginContext.java:194) > at java.base/javax.security.auth.login.LoginContext$4.run(LoginContext.java:665) > at java.base/javax.security.auth.login.LoginContext$4.run(LoginContext.java:663) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:663) > at java.base/javax.security.auth.login.LoginContext.login(LoginContext.java:574) > at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71) > at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53) > at org.wildfly.security.sasl.gs2.Gs2SuiteChild.init(Gs2SuiteChild.java:102) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeClassMethod(JUnit4TestRunnerDecorator.java:92) > at mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:30) > at mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > at java.base/javax.security.auth.login.LoginContext.invoke(LoginContext.java:821) > at java.base/javax.security.auth.login.LoginContext.access$000(LoginContext.java:194) > at java.base/javax.security.auth.login.LoginContext$4.run(LoginContext.java:665) > at java.base/javax.security.auth.login.LoginContext$4.run(LoginContext.java:663) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.base/javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:663) > at java.base/javax.security.auth.login.LoginContext.login(LoginContext.java:574) > at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71) > at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53) > at org.wildfly.security.sasl.gs2.Gs2SuiteChild.init(Gs2SuiteChild.java:102) > {noformat} > [1] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2245) JGroup JDBC_PING is not clearing the crashed members

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2245?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2245: --------------------------- Fix Version/s: 4.0.10 > JGroup JDBC_PING is not clearing the crashed members > ---------------------------------------------------- > > Key: JGRP-2245 > URL: https://issues.jboss.org/browse/JGRP-2245 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.8 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Priority: Critical > Fix For: 4.0.10 > > > 1) In AWS cloud environments, IP address will be different when a node crashes and when a new cluster node gets recreated. > 2) In this situation, JGroup is not clearing logical_addr_cache and it gets confused, when we restart the cluster nodes. > 3)logical_addr_cache_max_size and the eviction did not work because, the cache is again getting updated from the ping and it never getting marked as removable. > I think the issue is > handleView method is always re writing the entire cache on view change to the db. So even if we clear the table with the help of above mentioned flags (remove_all_data_on_view_change && remove_old_coords_on_view_change) , its getting re written to the table. > // remove all files which are not from the current members > protected void handleView(View new_view, View old_view, boolean coord_changed) { > if(is_coord) { > if(coord_changed) { > if(remove_all_data_on_view_change) > removeAll(cluster_name); > else if(remove_old_coords_on_view_change) { > Address old_coord=old_view != null? old_view.getCreator() : null; > if(old_coord != null) > remove(cluster_name, old_coord); > } > } > if(coord_changed || View.diff(old_view, new_view)[1].length > 0) { > writeAll(); > if(remove_all_data_on_view_change || remove_old_coords_on_view_change) > startInfoWriter(); > } > } > else if(coord_changed) // I'm no longer the coordinator > remove(cluster_name, local_addr); > } > 4) Because of the crashed members (non existing ip address), we are getting lot of socket timeouts > sendToMembers of TP is trying to send messages to old crashed members and writing error logs while startup. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2216) [DMN Editor] Decision Table Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2216?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2216: -------------------------------- QE Status: VERIFIED (was: ON_QA) > [DMN Editor] Decision Table Definition is not saved > --------------------------------------------------- > > Key: DROOLS-2216 > URL: https://issues.jboss.org/browse/DROOLS-2216 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2215) [DMN Editor] Function Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2215?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2215: -------------------------------- QE Status: VERIFIED (was: ON_QA) > [DMN Editor] Function Definition is not saved > --------------------------------------------- > > Key: DROOLS-2215 > URL: https://issues.jboss.org/browse/DROOLS-2215 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2217: ------------------------------------- [~tari_manga] Hi, I checked this with your latest changes done in DROOLS-1956, but this issue is still reproducible, I updated the steps for reproduce. > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Context Entry Definition is not saved

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2217: -------------------------------- Steps to Reproduce: # Create new DMN diagram # Add Decision node # Open Decision node properties # Configure this Decision node as Context Entry # Save DMN diagram # Reopen the DMN Diagram # Check the Decision node properties # The Decision node won't be configured as a Context Entry more # Check server log, there will be: [^error.log] was: # Create new DMN diagram # Add Decision node # Open Decision node properties # Configure this Decision node as Context Entry # Save DMN diagram # Reopen the DMN Diagram # Check the Decision node properties # The Decision node won't be configured as a Context Entry more > [DMN Editor] Context Entry Definition is not saved > -------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018