August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2373) SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range

by Radoslav Husar (Jira)

Radoslav Husar created JGRP-2373: ------------------------------------ Summary: SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range Key: JGRP-2373 URL: https://issues.jboss.org/browse/JGRP-2373 Project: JGroups Issue Type: Bug Reporter: Radoslav Husar Assignee: Bela Ban e.g. {{<SSL_KEY_EXCHANGE port_range="0"/>}} yields the following {noformat} 15:12:38,303 ERROR [org.jgroups.protocols.SSL_KEY_EXCHANGE] (ServerService Thread Pool -- 72) failed becoming key server: java.lang.IllegalStateException: found no valid port to bind to in range [2157-2157] at org.jgroups.protocols.SSL_KEY_EXCHANGE.createServerSocket(SSL_KEY_EXCHANGE.java:339) at org.jgroups.protocols.SSL_KEY_EXCHANGE.becomeKeyserver(SSL_KEY_EXCHANGE.java:304) at org.jgroups.protocols.SSL_KEY_EXCHANGE.handleView(SSL_KEY_EXCHANGE.java:287) at org.jgroups.protocols.KeyExchange.down(KeyExchange.java:45) at org.jgroups.protocols.Encrypt.down(Encrypt.java:132) at org.jgroups.protocols.ASYM_ENCRYPT.down(ASYM_ENCRYPT.java:122) at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:327) at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:696) at org.jgroups.protocols.pbcast.ClientGmsImpl.becomeSingletonMember(ClientGmsImpl.java:252) at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:83) at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) at org.jgroups.protocols.FRAG3.down(FRAG3.java:135) at org.jgroups.protocols.FORK.down(FORK.java:109) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) at org.jgroups.JChannel.down(JChannel.java:627) at org.jgroups.JChannel._connect(JChannel.java:855) at org.jgroups.JChannel.connect(JChannel.java:352) at org.jgroups.JChannel.connect(JChannel.java:343) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2373) SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2373?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned JGRP-2373: ------------------------------------ Assignee: Radoslav Husar (was: Bela Ban) > SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range > ------------------------------------------------------------------------ > > Key: JGRP-2373 > URL: https://issues.jboss.org/browse/JGRP-2373 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 4.1.4 > > > e.g. {{<SSL_KEY_EXCHANGE port_range="0"/>}} yields the following > {noformat} > 15:12:38,303 ERROR [org.jgroups.protocols.SSL_KEY_EXCHANGE] (ServerService Thread Pool -- 72) failed becoming key server: java.lang.IllegalStateException: found no valid port to bind to in range [2157-2157] > at org.jgroups.protocols.SSL_KEY_EXCHANGE.createServerSocket(SSL_KEY_EXCHANGE.java:339) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.becomeKeyserver(SSL_KEY_EXCHANGE.java:304) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.handleView(SSL_KEY_EXCHANGE.java:287) > at org.jgroups.protocols.KeyExchange.down(KeyExchange.java:45) > at org.jgroups.protocols.Encrypt.down(Encrypt.java:132) > at org.jgroups.protocols.ASYM_ENCRYPT.down(ASYM_ENCRYPT.java:122) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:327) > at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:696) > at org.jgroups.protocols.pbcast.ClientGmsImpl.becomeSingletonMember(ClientGmsImpl.java:252) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:83) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FRAG3.down(FRAG3.java:135) > at org.jgroups.protocols.FORK.down(FORK.java:109) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) > at org.jgroups.JChannel.down(JChannel.java:627) > at org.jgroups.JChannel._connect(JChannel.java:855) > at org.jgroups.JChannel.connect(JChannel.java:352) > at org.jgroups.JChannel.connect(JChannel.java:343) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2373) SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2373?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2373: --------------------------------- Affects Version/s: 4.1.3 > SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range > ------------------------------------------------------------------------ > > Key: JGRP-2373 > URL: https://issues.jboss.org/browse/JGRP-2373 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 4.1.4 > > > e.g. {{<SSL_KEY_EXCHANGE port_range="0"/>}} yields the following > {noformat} > 15:12:38,303 ERROR [org.jgroups.protocols.SSL_KEY_EXCHANGE] (ServerService Thread Pool -- 72) failed becoming key server: java.lang.IllegalStateException: found no valid port to bind to in range [2157-2157] > at org.jgroups.protocols.SSL_KEY_EXCHANGE.createServerSocket(SSL_KEY_EXCHANGE.java:339) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.becomeKeyserver(SSL_KEY_EXCHANGE.java:304) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.handleView(SSL_KEY_EXCHANGE.java:287) > at org.jgroups.protocols.KeyExchange.down(KeyExchange.java:45) > at org.jgroups.protocols.Encrypt.down(Encrypt.java:132) > at org.jgroups.protocols.ASYM_ENCRYPT.down(ASYM_ENCRYPT.java:122) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:327) > at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:696) > at org.jgroups.protocols.pbcast.ClientGmsImpl.becomeSingletonMember(ClientGmsImpl.java:252) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:83) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FRAG3.down(FRAG3.java:135) > at org.jgroups.protocols.FORK.down(FORK.java:109) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) > at org.jgroups.JChannel.down(JChannel.java:627) > at org.jgroups.JChannel._connect(JChannel.java:855) > at org.jgroups.JChannel.connect(JChannel.java:352) > at org.jgroups.JChannel.connect(JChannel.java:343) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2373) SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2373?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2373: --------------------------------- Fix Version/s: 4.1.4 > SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range > ------------------------------------------------------------------------ > > Key: JGRP-2373 > URL: https://issues.jboss.org/browse/JGRP-2373 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.3 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 4.1.4 > > > e.g. {{<SSL_KEY_EXCHANGE port_range="0"/>}} yields the following > {noformat} > 15:12:38,303 ERROR [org.jgroups.protocols.SSL_KEY_EXCHANGE] (ServerService Thread Pool -- 72) failed becoming key server: java.lang.IllegalStateException: found no valid port to bind to in range [2157-2157] > at org.jgroups.protocols.SSL_KEY_EXCHANGE.createServerSocket(SSL_KEY_EXCHANGE.java:339) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.becomeKeyserver(SSL_KEY_EXCHANGE.java:304) > at org.jgroups.protocols.SSL_KEY_EXCHANGE.handleView(SSL_KEY_EXCHANGE.java:287) > at org.jgroups.protocols.KeyExchange.down(KeyExchange.java:45) > at org.jgroups.protocols.Encrypt.down(Encrypt.java:132) > at org.jgroups.protocols.ASYM_ENCRYPT.down(ASYM_ENCRYPT.java:122) > at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:553) > at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:581) > at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:327) > at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:696) > at org.jgroups.protocols.pbcast.ClientGmsImpl.becomeSingletonMember(ClientGmsImpl.java:252) > at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:83) > at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40) > at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1044) > at org.jgroups.protocols.FlowControl.down(FlowControl.java:295) > at org.jgroups.protocols.FRAG3.down(FRAG3.java:135) > at org.jgroups.protocols.FORK.down(FORK.java:109) > at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928) > at org.jgroups.JChannel.down(JChannel.java:627) > at org.jgroups.JChannel._connect(JChannel.java:855) > at org.jgroups.JChannel.connect(JChannel.java:352) > at org.jgroups.JChannel.connect(JChannel.java:343) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4458) String to Boolean coercion doesn't work in executable model

by Tibor Zimanyi (Jira)

Tibor Zimanyi created DROOLS-4458: ------------------------------------- Summary: String to Boolean coercion doesn't work in executable model Key: DROOLS-4458 URL: https://issues.jboss.org/browse/DROOLS-4458 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.25.0.Final Reporter: Tibor Zimanyi Assignee: Tibor Zimanyi When having constraint like this: Person(booleanAttribute == "true") a build using executable model ends with an exception [1]. This is because the constraint parser doesn't coerce "true" to a boolean true. [1] https://gist.github.com/baldimir/e0f1aa27d194b750148f779370d13560 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-941) Kiali is now available without /kiali suffix in URL

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-941?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-941. --------------------------------- Resolution: Done https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/... > Kiali is now available without /kiali suffix in URL > --------------------------------------------------- > > Key: SWSQE-941 > URL: https://issues.jboss.org/browse/SWSQE-941 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Blocker > Labels: infrastructure > > Kiali is from RC1 available without /kiali suffix in URL. We need to find out why and update our pipelines -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Petr Sakar (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Petr Sakar commented on WFLY-12409: ----------------------------------- [~emmartins] your arguments are true only in case JBoss Specs BOM is discontinued > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Petr Sakar (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Petr Sakar commented on WFLY-12409: ----------------------------------- [~emmartins] I've looked at the PR. It means we have to change procedure which is automatically synchronizing versions between projects in release. > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on WFLY-12409: ---------------------------------------- [~psakar] please look at the PR, you don't need to change anything other than stop caring about jboss spec BOM version for the import > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Petr Sakar (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Petr Sakar commented on WFLY-12409: ----------------------------------- [~emmartins] unless it is clear what will happen to JBoss Specs BOM this issue only means more work (we have to change existing automated version propagation) without actually bringing anything > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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