2 Replies Latest reply on Jun 16, 2017 8:46 AM by Sathya

    Openfire Clustering timeout - Not accepting new connections

    Sathya

      I have been trying to connect two openfire nodes using hazelcast clustering. After successful setup and execution, it started throwing out time out exception and not accepting any new connections. Any help or directions on this ? Do we require any tweaks on the configuration?

       

      Following is the configuration:

       

      <hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.5.xsd"
                 xmlns="http://www.hazelcast.com/schema/config"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          ...
          ... 
          <properties>
            <property name="hazelcast.logging.type">slf4j</property>
            <property name="hazelcast.operation.call.timeout.millis">30000</property>
            <property name="hazelcast.memcache.enabled">false</property>
            <property name="hazelcast.rest.enabled">false</property>
          </properties>
          <management-center enabled="false"/>
          <network>
              <port auto-increment="true" port-count="100">5701</port>
              <outbound-ports>
                  <ports>0</ports>
              </outbound-ports>
              <join>
                  <multicast enabled="false"/>
                  <tcp-ip enabled="true">
                      <member>10.4.xxx.xxx:5701</member>
                      <member>10.3.xxx.xxx:5701</member>
                  </tcp-ip>
                  <aws enabled="false"/>
              </join>
              <interfaces enabled="false">
                  <interface>10.10.1.*</interface>
              </interfaces>
              <ssl enabled="false"/>
              <socket-interceptor enabled="false"/>
              <symmetric-encryption enabled="false">
      ...
      ...

       

      Current users count:

       

      Openfire version: 4.0.2

      Hazelcast plugin version: 2.2.0

      Hazelcast version: 3.5.1

       

       

      Following are the error snapshot