Hi All,
I am trying to implement a cluster with 3 nodes using Tomcat and Axis2. Also i have a state which i write to MessageContext. Thus i wanted, Axis2 to replicate above MessageContext among all nodes within the cluster. To do this i changed Axis2 XML and also attached MessageContext as a replication context. But it seems the property that i am in serting into the MessageContext is not visible to other nodes in the cluster.
<stateManager class="org.apache.axis2.clustering.state.DefaultStateManager"
                     enable="true">
           <replication>
               <defaults>
                   <exclude name="local_*"/>
                   <exclude name="LOCAL_*"/>
               </defaults>
<context class="org.apache.axis2.context.ConfigurationContext">
                   <exclude name="local_*"/>
                   <exclude name="UseAsyncOperations"/>
                   <exclude name="SequencePropertyBeanMap"/>
               </context>
<context class="org.apache.axis2.context.ServiceGroupContext">
                   <exclude name="local_*"/>
                   <exclude name="my.sandesha.*"/>
               </context>
               <context class="org.apache.axis2.context.ServiceContext">
                   <exclude name="local_*"/>
                   <exclude name="my.sandesha.*"/>
               </context>
               <context class="org.apache.axis2.context.MessageContext">
                   <exclude name="local_*"/>
               </context>
           </replication>
       </stateManager>

I have following questions related to this issue,

1. Can we replicate MessageContexts ? If so how ? Above mentioned configuration didnt work 2. When does Axis2 nodes are exchanging altered contexts? Ex :- "Is it before sending a message to a server or after sending a message, etc ...")"

Appreciate if someone can give feedback.

Thank you
AmilaJ



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to