Ramakanta Sahoo wrote:In cluster config tab I'm only able to see session replication between two clusters not between servers.
A'm using WL10 Please suggest how to achieve session replication between servers in a cluster.
I too looking for that one, I have already put this question in forums somebody has give the following solution
in your weblogic.xml you need to have a section like(take care you use whatever namespace prefix you have specified in weblogic.xml, e.g. wls: in the snippet below)
you can use the store type as replicated/replicated_if_clustered/sync-replication-across-cluster/async-replication-across-cluster for In memory replication.
But I have included weblogic.xml file as part web application when I deploy this applicaiton in the cluster I got the following exception
weblogic.management.DeploymentException: Deployer:149003Unable to access application source information in 'C:\Weblogic10.3\bea\user_projects\domains\Cluster_domain\servers\MHS_1\stage\HelloWorld\HelloWorld.war' for application 'HelloWorld'. The specific error is: Deployer:149158No application files exist at 'C:\Weblogic10.3\bea\user_projects\domains\Cluster_domain\servers\MHS_1\stage\HelloWorld\HelloWorld.war'..
Marcos Maia wrote:Objects in session have to be Serializable to work properly.
How are you testing this? Are you using a load balancer? A proxy?
Thanks for reply.
How to enable Serializable in session??? please send me steps.
starts both servers in a cluster. login to my application and checks which server got my application log. then i shutsdown the server that got the client log as that server is accessed that moment. and clicks in my application which is already logged in but it gets logged out and i have to login to continue normal operations.
In Apache I'm using wl_22.so file.
Joined: Jan 06, 2001
All objects placed in session should implement Serializable interface. In collections objects in it should be serializable.
Did you have configured a cluster already? Are you using multicast or unicast cluster?
yes I have configured cluster already. the problem is session replication between servers in the cluster. one server should be capable of handling a request without getting logged out. If session replication is enabl;es then the user wont know which server he is accessesing or any server went down or not as he will never be logged out if the servicing server goes down as the other server will be able continue from the server1's leftout without getting that user logged out.
Joined: Jan 06, 2001
You have some wrong configuration in your cluster. I have worked with clusters in weblogic since version 6 (2002) and allways work. That's why I'm asking about your cluster configuration. Are you using multicast or unicast cluster? How did you configure it?
Marcos Maia wrote:You have some wrong configuration in your cluster. I have worked with clusters in weblogic since version 6 (2002) and allways work. That's why I'm asking about your cluster configuration. Are you using multicast or unicast cluster? How did you configure it?