Problem in Session Replication in JBoss EAP 6.4 + Apache mod_cluster

[gian.honorio]

Hello, I am having some problems trying to configure session replication in JBoss EAP 6.4 domain mode + Apache with mod_cluster, I have already followed several guides and tutorials and tried several different configurations, but without success. The cluster works correctly, only the sessions that are not replicated.

Here is the cluster topology:

And here are some of the important parts of configuration files:

http.conf

<IfModule manager_module>

        Listen 192.168.8.91:8080

        ManagerBalancerName adapter-conectcor-cluster-group

        <VirtualHost 192.168.8.91:8080>

                <Location />

                        Require all granted

                </Location>

                TimeOut 30

                KeepAliveTimeout 5

                MaxKeepAliveRequests 0

                AdvertiseFrequency 5

                EnableMCPMReceive on

                <Location /modcluster_manager>

                        SetHandler mod_cluster-manager

                        Order deny,allow

                        Allow from 192.168.0.0/23

                        Require all granted

                </Location>

        </VirtualHost>

        <VirtualHost *:80>

                ProxyPreserveHost On

                ProxyPass /server-status !

                ProxyPass / http://192.168.8.91:8080/counter/

                ProxyPassReverse / http://192.168.8.91:8080/counter/

                ProxyPassReverseCookiePath / /

                <Location /server-status>

                        SetHandler server-status

                        Order deny,allow

                        Deny from all

                        Allow from 192.168.0.0/23

                </Location>

        </VirtualHost>

</IfModule>

domain.xml

<subsystem xmlns="urn:jboss:domain:modcluster:1.2">

     <mod-cluster-config advertise-socket="modcluster" proxy-list="192.168.8.91:8080" sticky-session="true" sticky-session-force="false" balancer="adapter-conectcor-cluster-group" connector="ajp">

          <dynamic-load-provider>

               <load-metric type="busyness"/>

          </dynamic-load-provider>

     </mod-cluster-config>

</subsystem>

<cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">

     <transport lock-timeout="60000"/>

     <replicated-cache name="repl" mode="ASYNC" batching="true">

          <file-store/>

     </replicated-cache>

     <replicated-cache name="sso" mode="SYNC" batching="true"/>

     <distributed-cache name="dist" l1-lifespan="0" mode="ASYNC" batching="true">

          <file-store/>

     </distributed-cache>

</cache-container>

For the tests I'm using the attached project "counter.war", and if any other part of any configuration file is needed just ask. I appreciate any kind of help or tip.

[pferraro]

How have you determined that your sessions are not replicating?

[gian.honorio]

Hi pferraro , first I tested it on my own application, logging into the system and then stoping the node that I logged in to, so I reloaded the page and she redirected me to login again, showing that the session was lost. Then to make sure it was not a problem in my application I followed the guide at this link https://access.redhat.com/solutions/46373 and did the same procedure, and yet the session was lost.

[pferraro]

The issue may not necessarily be with replication of the session, but rather with security configuration.  Can you describe your authentication mechanism?

[gian.honorio]

After doing a lot of research, I was able to figure out what the problem was and then solve it.

When I started the JBoss of the nodes the following message was displayed:

And after the server was started, the following message starts to appears periodically:

He probably displayed this message whenever he tried to replicate the sessions and could not access the interface to transmitting it. So based on this link https://access.redhat.com/solutions/486433 I configured the -Djgroups.bind_addr parameter of the nodes, to bind to the IP address of the host itself, and that's it, everything started to work.