jboss7.x - Session replication on EAP JBOSS 6.0 -

i working on struts 2 framework eap jboss 6. project session variables stored , retrieved using 'http session map'. when moved on domain mode of jboss clustering session values lost while switching between different nodes of server. configured sticky session , stored session values in cookies. though able retrieve value cookie on first request, http session lost. i'm using apache mod cluster clustering configuration follows.

loadmodule proxy_module modules/mod_proxy.so loadmodule proxy_ajp_module modules/mod_proxy_ajp.so loadmodule proxy_http_module modules/mod_proxy_http.so  loadmodule proxy_cluster_module modules/mod_proxy_cluster.so  loadmodule manager_module modules/mod_manager.so loadmodule slotmem_module modules/mod_slotmem.so loadmodule advertise_module modules/mod_advertise.so  listen 192.168.5.30:80  <virtualhost 192.168.5.30:80>  managerbalancername my-cluster  servername nsn <directory />     order deny,allow     allow </directory> <location /mod_cluster-manager>     sethandler mod_cluster-manager     order deny,allow     allow </location> enablemcpmreceive #proxypass / balancer://my-cluster stickysession=jsessionid|jsessionid nofailover=on  proxypass / balancer://my-cluster stickysession=off nofailover=on  proxypassreverse / balancer://my-cluster  proxypreservehost on        keepalivetimeout 60        serveradvertise on 

now searched , found mod_cluster(https://github.com/modcluster/mod_cluster). in mentioned put folder 'deploy directory of jboss server profile'. in eap jboss 6.0 domain mode don't know deploy directory , how configure mod cluster?

i solved session replication configuring jboss-web.xml under web-inf folder follows...

<?xml version="1.0" encoding="utf-8"?> <jboss-web version="6.0"        xmlns="http://www.jboss.com/xml/ns/javaee"        xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"        xsi:schemalocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_6_0.xsd"> <replication-config>     <!-- default value set_and_non_primitive_get, therefore byte array carrying data considered non-primitive , cause replication in read scenario. -->     <replication-trigger>set</replication-trigger>      <!-- replicating entire session default. -->     <replication-granularity>session</replication-granularity>    <replication-mode>synchronous</replication-mode> </replication-config> 

in case no need use cookies store values...