如何使用Openshift Wildfly 8 Cartridge打开JChannel（JGroups） [英] How to open a JChannel (JGroups) using Openshift Wildfly 8 Cartridge

问题描述

我们正在Wildfly-Openshift-Cartridge中开发在Wildfly 8上运行的Java-EE应用程序。
Openshift应用程序设置为缩放，因此，多个JVM节点将作为集群运行。

We are developing a Java-EE Application running on Wildfly 8 in the Wildfly-Openshift-Cartridge. The Openshift Application is set to scaled, therefore, more than one JVM node will be running as a cluster.

不同节点之间的通信，我喜欢使用JGroups。但是，即使JGroups本身似乎有效，我也无法打开新的JChannel。如果我将应用程序本地部署到例如，应用程序本身也可以工作。 3个wildfly独立实例。

The communicate between the different nodes, I like to use JGroups. However, I fail to open a new JChannel even though the JGroups itself seems to work. The application itself does also work, if I deploy the application locally to e.g. 3 wildfly standalone instances.

wildfly-cartrige的默认standalone.xml包含JGroups的配置：

The default standalone.xml of the wildfly-cartrige contains already a configuration for JGroups:

....
<subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="tcp">
    <stack name="tcp">
        <transport type="TCP" socket-binding="jgroups-tcp">
            <property name="external_addr">${env.OPENSHIFT_GEAR_DNS}</property>
            <property name="external_port">${env.OPENSHIFT_WILDFLY_CLUSTER_PROXY_PORT}</property>
            <property name="bind_port">${env.OPENSHIFT_WILDFLY_CLUSTER_PORT}</property>
            <property name="bind_addr">${env.OPENSHIFT_WILDFLY_IP}</property>
            <property name="defer_client_bind_addr">true</property>
        </transport>
        <protocol type="TCPPING">
            <property name="timeout">30000</property>
            <property name="initial_hosts">${env.OPENSHIFT_WILDFLY_CLUSTER}</property>
            <property name="port_range">0</property>
            <property name="num_initial_members">1</property>
        </protocol>
        <protocol type="MERGE2"/>
        <protocol type="FD"/>
        <protocol type="VERIFY_SUSPECT"/>
        <protocol type="BARRIER"/>
        <protocol type="pbcast.NAKACK"/>
        <protocol type="UNICAST2"/>
        <protocol type="pbcast.STABLE"/>
        <protocol type="AUTH">
            <property name="auth_class">org.jgroups.auth.MD5Token</property>
            <property name="token_hash">SHA</property>
            <property name="auth_value">${env.OPENSHIFT_SECRET_TOKEN}</property>
        </protocol>
        <protocol type="pbcast.GMS"/>
        <protocol type="UFC"/>
        <protocol type="MFC"/>
        <protocol type="FRAG2"/>
        <!--protocol type="pbcast.STATE_TRANSFER"/>
        <protocol type="pbcast.FLUSH"/-->
    </stack>
</subsystem>
....

根据这个，默认堆栈应该是tcp - 这使得感觉，因为在OpenShift环境中不允许UDP多播。

According this, the default-stack shall be tcp - which makes sense, since UDP multicasting is not allowed in the OpenShift environment.

如果我将应用程序部署到OpenShift（缩放，有两个正在运行的齿轮），JGroups本身似乎在沟通JVM之间：来自wildfly / log / server.log的输出：

If I deploy the application to OpenShift (scaled, with two running gears), the JGroups itself seems to communicate between the JVMs: Output from wildfly/log/server.log:

....
INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 59) ISPN000078: Starting JGroups Channel
INFO  [stdout] (ServerService Thread Pool -- 59)
INFO  [stdout] (ServerService Thread Pool -- 59) -------------------------------------------------------------------
INFO  [stdout] (ServerService Thread Pool -- 59) GMS: address=xxx.rhcloud.com/ejb, cluster=ejb, physical address=172.30.0.163:62417
....
INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,shared=tcp) ISPN000094: Received new cluster view: [xxx.rhcloud.com/ejb|4] (1) xxx.rhcloud.com/ejb]
....
INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-6,shared=tcp) ISPN000094: Received new cluster view: [yyyy.rhcloud.com/ejb|5] (2) [xxx.rhcloud.com/ejb, 55b89cd750044609f0000043-xx.rhcloud.com/ejb]
...

这是开箱即用的，没有任何编程。

This works out of the box, without any own programming.

但是现在，我想打开一个JChannel，将消息从一个JVM发送给所有其他JVM。

But now, I want to open a JChannel to send messages from one JVM to all others.

...
import org.jgroups.*;
...
public class MyNotifier extends ReceiverAdapter
{
    ...

    JChannel channel;

    public void start()
    {
        try
        {
            channel = new JChannel();
            channel.setReceiver(this);
            channel.connect("MyNotifier");
        }
        catch (ChannelException e)
        {
            log.error("JGroups: Error starting channel.", e);
        }
    }

    public void receive(Message msg)
    {
        // process message
    }

    public void send(DataObject data)
    {
        Message msg = new Message(null, null, data);

        try
        {
            channel.send(msg);
        }
        catch (Exception e)
        {
            log.error("JGroups: Error sending message.", e);
        }
    }

    public void viewAccepted(View new_view)
    {
        log.info("JGroups: View accepted: " + new_view );
    }
}

期间引发异常channel = new JChannel（）：

INFO  [stdout] (ServerService Thread Pool -- 82) 72190 [ERROR] MyNotifier: JGroups: Error starting channel.
INFO  [stdout] (ServerService Thread Pool -- 82) org.jgroups.ChannelException: failed to start protocol stack
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.JChannel.startStack(JChannel.java:1787) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.JChannel.connect(JChannel.java:413) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.JChannel.connect(JChannel.java:388) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at xxxxx.MyNotifier.start(MyNotifier.java:41) [classes:?]
INFO  [stdout] (ServerService Thread Pool -- 82)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) [wildfly-ee-8.2.0.Final.jar!/:8.2.0.Final]
...
INFO  [stdout] (ServerService Thread Pool -- 82) Caused by: java.lang.Exception: problem creating sockets (bind_addr=localhost/127.0.0.1, mcast_addr=null)
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.protocols.UDP.start(UDP.java:238) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:990) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.JChannel.startStack(JChannel.java:1784) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    ... 136 more
INFO  [stdout] (ServerService Thread Pool -- 82) Caused by: java.lang.IllegalArgumentException: port out of range:65536
INFO  [stdout] (ServerService Thread Pool -- 82)    at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at java.net.InetSocketAddress.<init>(InetSocketAddress.java:188) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at java.net.DatagramSocket.<init>(DatagramSocket.java:299) ~[?:1.8.0_45]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:65) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:458) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.protocols.UDP.createSockets(UDP.java:342) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.protocols.UDP.start(UDP.java:234) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:990) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    at org.jgroups.JChannel.startStack(JChannel.java:1784) ~[jgroups-2.12.1.Final.jar:2.12.1.Final]
INFO  [stdout] (ServerService Thread Pool -- 82)    ... 136 more

似乎JChannel尝试使用UDP。但是如何让它在standalone.xml中使用什么设置为子系统？

It seems that JChannel tries to use even UDP. But how can I bring it to use what is setup as subsystem in the standalone.xml?

更多信息：
正如我在上面写的那样，JChannel是如果我使用UDP多播将应用程序部署到某些本地运行的wildfly实例，则会成功创建。然后我尝试在本地应用相同的堆栈配置，就像在OpenShift上一样，结果它仍然可以工作，但即使是UDP。所以我的 channel = new JChannel（）; 似乎不使用子系统配置中的设置。但为什么呢？

Some more information: As I wrote on top, JChannel is successfully created, if I deploy the application to some local running wildfly instances using UDP Multicasting. I then tried to apply locally the same stack configuration, as on OpenShift with the result that it still worked but even by UDP. So it seems that my channel = new JChannel(); does not use the settings from the subsystem configuration. But why?

编辑：

我明白了子系统的配置，即子系统中的default-stack设置与新的JChannel（）将使用的无关;因此，我尝试现在创建自己的tcp.xml。
但是，第一个问题是如何在此配置中使用环境变量（扩展到它们的值），例如我需要类似< TCP bind_addr = $ {env.OPENSHIFT_WILDFLY_IP} /> 的内容。我怎样才能实现这一目标？

I understood that the subsystem configuration i.e. the default-stack set in the subsystem has nothing to do with what new JChannel() will use; therefore, I try to create now my own tcp.xml. However, the first problem is how to use environment variables in this config (which expands to their value) e.g. I need something like <TCP bind_addr=${env.OPENSHIFT_WILDFLY_IP}/>. How can I achieve that?

第一步，我尝试插入修正正确值：

For the first step, I tried to insert the fix correct values:

<config xmlns="urn:org:jgroups"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/JGroups-3.3.xsd">
    <TCP
            external_addr="backend-evendingtest.rhcloud.com"
            external_port="62417"
            bind_port="7600"
            bind_addr="127.11.122.129"
            defer_client_bind_addr="true"/>

    <TCPPING timeout="3000"
             initial_hosts="backend-evendingtest.rhcloud.com[62417],55b89cd750044609f0000043-evendingtest.rhcloud.com[56432]"
             port_range="0"
             num_initial_members="1"/>
    <MERGE2/>
    <FD/>
    <VERIFY_SUSPECT/>
    <BARRIER/>
    <pbcast.NAKACK2
            use_mcast_xmit="false"/>
    <UNICAST3/>
    <pbcast.STABLE/>
    <AUTH auth_class="org.jgroups.auth.MD5Token"
          token_hash="SHA"
          auth_value="2QVXd4rUYmxOtZNlxsJ7fBbWb4J8eFJup39PSC1IZck1JHDr_y4qUzFZVqUzLVZ7rDHnZWPtOpyY4pTrPAZ__D06GHHz5Uq9D5ZPMtyHPkZuvRh3cWchUX3JxA5Qsq4B"/>
    <pbcast.GMS/>
    <MFC/>
    <FRAG2/>

...但我以一个例外情况失败：

...but I fail with an Exception:

java.net.BindException: Permission denied
      at java.net.PlainDatagramSocketImpl.bind0(Native Method)
      at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)
      at java.net.DatagramSocket.bind(DatagramSocket.java:392)
      at java.net.MulticastSocket.<init>(MulticastSocket.java:172)
      at java.net.MulticastSocket.<init>(MulticastSocket.java:136)
      at org.jgroups.util.DefaultSocketFactory.createMulticastSocket(DefaultSocketFactory.java:70)
      at org.jgroups.stack.DiagnosticsHandler.start(DiagnosticsHandler.java:83)
      at org.jgroups.protocols.TP.start(TP.java:1222)
      at org.jgroups.protocols.TCP.start(TCP.java:82)
      at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:952)
      at org.jgroups.JChannel.startStack(JChannel.java:864)

为什么在此跟踪中会出现类似'createMulticastSocket'的内容？ - 我不想使用UDP /多播......

Why is there somehting like 'createMulticastSocket' in this trace? - I do not want to use UDP / Multicasting...

提前感谢您的帮助！
- badera

Thanks in advance for help! - badera

推荐答案

新的JChannel（）使用默认配置，即udp.xml（在JGroups JAR中） ）。您收到的错误消息是因为JGroups无法绑定到127.0.0.1:0（临时端口）。

new JChannel() uses the default config, which is udp.xml (in the JGroups JAR). The error message you're getting is because JGroups can't bind to 127.0.0.1:0 (ephemeral port).

我建议重用Wildfly已经提供的频道，详见[1]。 IIRC，Wildfly 9实际上暴露了JGroups频道，但这可能还没有出现在8 ...

I suggest reuse the channel already provided by Wildfly, see [1] for details. IIRC, Wildfly 9 actually exposes the JGroups channel, but this may not yet be in 8...

[1] https://developer.jboss.org/wiki/ClusteringChangesInWildFly8

这篇关于如何使用Openshift Wildfly 8 Cartridge打开JChannel（JGroups）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！