[jboss-jira] [JBoss JIRA] (WFLY-10783) ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
Petr Kremensky (JIRA)
issues at jboss.org
Thu Aug 2 08:51:00 EDT 2018
Petr Kremensky created WFLY-10783:
-------------------------------------
Summary: ChannelServiceConfigurator failed to open a port while deploying kitchenskink qs on migrated server
Key: WFLY-10783
URL: https://issues.jboss.org/browse/WFLY-10783
Project: WildFly
Issue Type: Bug
Components: Clustering, Migration
Reporter: Petr Kremensky
Assignee: Paul Ferraro
Priority: Blocker
Attachments: jboss-kitchensink.war
Trying to deploy kitchensink quickstart on the server with configuration migrated from EAP 6.4.x fails with {{java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-ha.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG} ${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=web:migrate
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
deploy jboss-kitchensink.war
{noformat}
*Outcome*
{noformat}
14:44:13,799 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 56) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee-ejb: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee-ejb: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final]
Caused by: java.lang.IllegalStateException: java.lang.Exception: failed to open a port in range 55200-55200
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) [wildfly-clustering-service-14.0.0.Beta2-SNAPSHOT.jar:14.0.0.Beta2-SNAPSHOT]
... 7 more
Caused by: java.lang.Exception: failed to open a port in range 55200-55200
at org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:519)
at org.jgroups.protocols.UDP.createSockets(UDP.java:357)
at org.jgroups.protocols.UDP.start(UDP.java:300)
at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:861)
at org.jgroups.JChannel.startStack(JChannel.java:1023)
at org.jgroups.JChannel._preConnect(JChannel.java:886)
at org.jgroups.JChannel.connect(JChannel.java:390)
at org.jgroups.JChannel.connect(JChannel.java:384)
at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:112)
... 9 more
{noformat}
This works fine with EAP 7.1.3 as a TARGET_SERVER, thus marking as a blocker due to a regression.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list