This content has been marked as final. Show 12 replies
Are you using the Cross Cluster Replication or the Application is deployed on single cluster ?
Does that make a difference?
I am on a single cluster.
As Sandeep mentioned defiantly it make difference if you are using cross cluster Domain but as you mentioned that you are in single server.
Can you give me config.xml and weblogic.xml file to check where is missing.
In my config.xml, I have:
I already posted my weblogic.xml
Have you tried putting the value of <cluster-address> with all the servers address and port present in the cluster as mentioned below :
I tried adding my managed server IPs into <cluster-address>
It did not change anything.
What is the <cluster-address> entry supposed to do?
this cluster address will include list of the managed servers which are under same cluster.
so it should keep in this way.
I tried adding the t3:// prefix and it still doesn't work.
I was previously specifying in the web console:
Number Of Servers In Cluster Address: 3
Number of servers to be listed from this cluster when generating a cluster address automatically. This setting has no effect if Cluster Address is explicitly set.
Can you provide me the server log to check it.
I would say enable cluster debug and provide us the logs to check them.
What log messages should I expect to see in a proper cluster failover?
there would be mulitple mostly we can check Jsession ID which changes and it also give why the failover is not happening.
It is not necessary or the right practice to provide the protocol in front of WebLogic Cluster address.
It must look like ip1:port, ip2:port, ip3:port...
I suggest you to enable the cluster under debug tab of all cluster members (participating managed servers), run the test and look for specific messages related to replication. If you require assistance after that, you can post the log snippet here.