Remote outbound connection : heartbeat_interval

[a.durussel]

We are facing the same problem as mentioned in [WFLY-5534] Standalone EJB client resets connection after 5 minutes of inactivity - JBoss Issue Tracker  but concerning a remote-outbound-connection.

Let me explain the context:

We have a web application running on wildfly server 1 in DMZ that make EJB call through remote-outbound-connection in wildfly server 2 located in our internal network

There is a firewall monitoring traffic between DMZ and internal network that decides to drop packets of silent open TCP connections. Therefore we'd like to active the keep alive mechanism and use the heartbeat_interval to configure the frequency.

We configured our remote-outbound-connection with the following parameters in the remoting subsystem (standalone.xml) :

(this was working perfectly in old version of jboss)

<outbound-connections>

                <remote-outbound-connection name="pro-ejb-connection" outbound-socket-binding-ref="pro-ejb" username="jboss" security-realm="ejbRemoteRealm">

                    <properties>

                        <property name="SASL_POLICY_NOANONYMOUS" value="false"/>

                        <property name="SSL_ENABLED" value="false"/>

                        <property name="KEEP_ALIVE" value="true"/>

                        <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="60000"/>

                    </properties>

                </remote-outbound-connection>

</outbound-connections>

But this seems to not be read of transmitted correctly to the remoting layer and when remote connection are created, the heartbeat_interval is not set correctly.

We also debug the creation of remote connections in class org.jboss.remoting3.remote.RemoteConnection and the optionMap which is read to initialize (line 75) heartbeat_interval is always empty.

Does anyone has a solution to configure the heartbeat_interval of remote connection correctly from standalone.xml ?

Thanks in advance for you help.

[jaikiran]

Which version of WildFly is this failing on? And are you sure this outbound connection is indeed what's being used?

[a.durussel]

We are using Wildfly 11

Yes we are sure because the EJB is only available on this remote server. Do you have any process to double check that it's this remote connection that is used ?  

[jaikiran]

A quick glance at WildFly source code indicates there's been some change to this part of the code. I am not sure if this is supported anymore and/or whether this is a bug. You might want to file a JIRA - JBoss Issue Tracker  explaining your use case and attaching a simple example which reproduces this.

[jaikiran]

I just realized this is posted in the JBoss Remoting forum. Someone with the right permissions would have to move this to the WildFly forum, which is where this is appropriate.