May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Description: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 * JGRP-2477 Reintroduce support for configuring a JChannel via URL * JGRP-2469 GossipRouter: make GraalVM-compliant Changes without Jiras: * Fixed NPE in TUNNEL - https://github.com/belaban/JGroups/commit/533b40917d7581a8901968e9a41a5fe... * New logic to handle exceptions in TcpConnection.run() - https://github.com/belaban/JGroups/commit/f3e31ece61e22cf8b7890837f4f2156... Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... was: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 * JGRP-2477 Reintroduce support for configuring a JChannel via URL * JGRP-2469 GossipRouter: make GraalVM-compliant Changes without Jiras: * Fixed NPE in TUNNEL https://github.com/belaban/JGroups/commit/533b40917d7581a8901968e9a41a5fe... * New logic to handle exceptions in TcpConnection.run() - https://github.com/belaban/JGroups/commit/f3e31ece61e22cf8b7890837f4f2156... Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345577 > * JGRP-2477 Reintroduce support for configuring a JChannel via URL > * JGRP-2469 GossipRouter: make GraalVM-compliant > Changes without Jiras: > * Fixed NPE in TUNNEL - https://github.com/belaban/JGroups/commit/533b40917d7581a8901968e9a41a5fe... > * New logic to handle exceptions in TcpConnection.run() - https://github.com/belaban/JGroups/commit/f3e31ece61e22cf8b7890837f4f2156... > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Description: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 * JGRP-2477 Reintroduce support for configuring a JChannel via URL * JGRP-2469 GossipRouter: make GraalVM-compliant Changes without Jiras: * Fixed NPE in TUNNEL https://github.com/belaban/JGroups/commit/533b40917d7581a8901968e9a41a5fe... * New logic to handle exceptions in TcpConnection.run() - https://github.com/belaban/JGroups/commit/f3e31ece61e22cf8b7890837f4f2156... Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... was: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 * JGRP-2477 Reintroduce support for configuring a JChannel via URL * JGRP-2469 GossipRouter: make GraalVM-compliant Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345577 > * JGRP-2477 Reintroduce support for configuring a JChannel via URL > * JGRP-2469 GossipRouter: make GraalVM-compliant > Changes without Jiras: > * Fixed NPE in TUNNEL https://github.com/belaban/JGroups/commit/533b40917d7581a8901968e9a41a5fe... > * New logic to handle exceptions in TcpConnection.run() - https://github.com/belaban/JGroups/commit/f3e31ece61e22cf8b7890837f4f2156... > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Description: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... was: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345542 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345577 > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Description: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 * JGRP-2477 Reintroduce support for configuring a JChannel via URL * JGRP-2469 GossipRouter: make GraalVM-compliant Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... was: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345577 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345577 > * JGRP-2477 Reintroduce support for configuring a JChannel via URL > * JGRP-2469 GossipRouter: make GraalVM-compliant > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Description: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345542 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... was: Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345542 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.2.Final...JGroups-... > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345542 > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.3.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13491: ------------------------------------- Summary: Upgrade JGroups to 4.2.4.Final Key: WFLY-13491 URL: https://issues.redhat.com/browse/WFLY-13491 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 20.0.0.Beta1 Issues resolved https://issues.redhat.com/projects/JGRP/versions/12345542 Code changes https://github.com/belaban/JGroups/compare/JGroups-4.2.2.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/13214) > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345542 > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.2.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13491) Upgrade JGroups to 4.2.4.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13491?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13491: ---------------------------------- Priority: Major (was: Minor) > Upgrade JGroups to 4.2.4.Final > ------------------------------ > > Key: WFLY-13491 > URL: https://issues.redhat.com/browse/WFLY-13491 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Issues resolved > https://issues.redhat.com/projects/JGRP/versions/12345542 > Code changes > https://github.com/belaban/JGroups/compare/JGroups-4.2.2.Final...JGroups-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5345) Class loading issue in Eclipse Equinox OSGi container

by Richard Schurig (Jira)

[ https://issues.redhat.com/browse/DROOLS-5345?page=com.atlassian.jira.plug... ] Richard Schurig updated DROOLS-5345: ------------------------------------ Description: When using Drools inside an *Equinox* OSGi container (Oxygen, org.eclipse.osgi-3.12.0.v20170512-1932.jar) the logic inside {{org.drools.relective.classloader.ProjectClassLoader#isOsgiClassLoader}} does not work properly, i.e. the OSGi runtime is not detected. This leads to "The Eclipse JDT Core jar is not in the classpath" because the shaded and packed compiler classes cannot be found. Cause of the problem seems to be the fact that the {{EquinoxClassLoader}} does not implement {{BundleReference}} directly *but so does its superclass*. I tried and patched {{ProjectClassLoader}} with the following snippet and this seems to work: {code:java} private static boolean isOsgiClassLoader(final ClassLoader cl) { Class<?> clc = cl.getClass(); while (clc != null && !clc.equals(ClassLoader.class)) { if (Stream.of(clc.getInterfaces()).map(Class::getSimpleName).anyMatch(name -> name.equals("BundleReference"))) { return true; } clc = clc.getSuperclass(); } return false; } {code} was: When using Drools inside an *Equinox* OSGi container (Oxygen, org.eclipse.osgi-3.12.0.v20170512-1932.jar) the logic inside `org.drools.relective.classloader.ProjectClassLoader#isOsgiClassLoader` does not work properly, i.e. the OSGi runtime is not detected. This leads to "The Eclipse JDT Core jar is not in the classpath" because the shaded and packed compiler classes cannot be found. Cause of the problem seems to be the fact that the `EquinoxClassLoader`does not implement `BundleReference` directly *but so does its superclass*. I tried and patched `ProjectClassLoader` with the following snippet and this seems to work: {code:java} private static boolean isOsgiClassLoader(final ClassLoader cl) { Class<?> clc = cl.getClass(); while (clc != null && !clc.equals(ClassLoader.class)) { if (Stream.of(clc.getInterfaces()).map(Class::getSimpleName).anyMatch(name -> name.equals("BundleReference"))) { return true; } clc = clc.getSuperclass(); } return false; } {code} > Class loading issue in Eclipse Equinox OSGi container > ----------------------------------------------------- > > Key: DROOLS-5345 > URL: https://issues.redhat.com/browse/DROOLS-5345 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.37.0.Final > Reporter: Richard Schurig > Assignee: Mario Fusco > Priority: Major > > When using Drools inside an *Equinox* OSGi container (Oxygen, org.eclipse.osgi-3.12.0.v20170512-1932.jar) the logic inside {{org.drools.relective.classloader.ProjectClassLoader#isOsgiClassLoader}} does not work properly, i.e. the OSGi runtime is not detected. This leads to "The Eclipse JDT Core jar is not in the classpath" because the shaded and packed compiler classes cannot be found. > Cause of the problem seems to be the fact that the {{EquinoxClassLoader}} does not implement {{BundleReference}} directly *but so does its superclass*. I tried and patched {{ProjectClassLoader}} with the following snippet and this seems to work: > {code:java} > private static boolean isOsgiClassLoader(final ClassLoader cl) { > Class<?> clc = cl.getClass(); > while (clc != null && !clc.equals(ClassLoader.class)) { > if (Stream.of(clc.getInterfaces()).map(Class::getSimpleName).anyMatch(name -> name.equals("BundleReference"))) { > return true; > } > clc = clc.getSuperclass(); > } > return false; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5345) Class loading issue in Eclipse Equinox OSGi container

by Richard Schurig (Jira)

Richard Schurig created DROOLS-5345: --------------------------------------- Summary: Class loading issue in Eclipse Equinox OSGi container Key: DROOLS-5345 URL: https://issues.redhat.com/browse/DROOLS-5345 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.37.0.Final Reporter: Richard Schurig Assignee: Mario Fusco When using Drools inside an *Equinox* OSGi container (Oxygen, org.eclipse.osgi-3.12.0.v20170512-1932.jar) the logic inside `org.drools.relective.classloader.ProjectClassLoader#isOsgiClassLoader` does not work properly, i.e. the OSGi runtime is not detected. This leads to "The Eclipse JDT Core jar is not in the classpath" because the shaded and packed compiler classes cannot be found. Cause of the problem seems to be the fact that the `EquinoxClassLoader`does not implement `BundleReference` directly *but so does its superclass*. I tried and patched `ProjectClassLoader` with the following snippet and this seems to work: {code:java} private static boolean isOsgiClassLoader(final ClassLoader cl) { Class<?> clc = cl.getClass(); while (clc != null && !clc.equals(ClassLoader.class)) { if (Stream.of(clc.getInterfaces()).map(Class::getSimpleName).anyMatch(name -> name.equals("BundleReference"))) { return true; } clc = clc.getSuperclass(); } return false; } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020