[jboss-jira] [JBoss JIRA] (JGRP-1972) Problem with tcp-cluster in Wildfly 8.2.1.Final

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124146#comment-13124146 ] 

Bela Ban commented on JGRP-1972:
--------------------------------

I don't think a cluster was started, as this is done just-in-time when (e.g.) a distributable app is deployed. You could use -Djgroups.bind_addr=x.x.x.x to pick an interface to bind to.
This is a Wildfly question, not a JGroups question; I suggest ask on the Wildfly mailing list.

> Problem with tcp-cluster in Wildfly 8.2.1.Final
> -----------------------------------------------
>
>                 Key: JGRP-1972
>                 URL: https://issues.jboss.org/browse/JGRP-1972
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Manu Forensic
>            Assignee: Bela Ban
>         Attachments: server.log, standalone-ha.xml
>
>
> I´ve some problems with a cluster tcp configuration with wildfly 8.2.1.Final. This is my standalone-ha.xml (attached file).
> Now when I try to start server in standalone mode:
> # ./standalone.sh -c standalone-ha.xml  -b 10.10.10.1 & (server.log attached file).
> It seems not starting a TCP socket in port 7600:
> # netstat -nlpt|grep java
> tcp        0      0 127.0.0.1:9990              0.0.0.0:*                   LISTEN      30348/java
> tcp        0      0 10.10.10.1:8009           0.0.0.0:*                   LISTEN      30348/java
> tcp        0      0 10.10.10.1:8080           0.0.0.0:*                   LISTEN      30348/java
>  
>  
> However there is multicast in UDP:
>  
> # netstat -nlpu|grep java
> udp        0      0 224.0.1.105:23364           0.0.0.0:*                               30348/java
> Where is the problem?
> Thank for your support
> Best regards.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)