question about session replication in weblogic cluster

[Robert Strong]

hi, I'm using BEA Weblogic8.1SP5 collocated clustered architecture, there're two managed server, and one proxy server in the cluster.

I've configured in weblogic.xml for session replications
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>

but to test failover, I shutdown the primary server(locate the primary server by log4j) in the middle of a session, then I keep making request on web page wishing to recover the session from the secondary server. but I received an exception like below:

Error 500--Internal Server Error
java.lang.RuntimeException: WebApp with contextPath: /bigrez not found in the secondary server
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.cluster.replication.ReplicationManager_815_WLStub.create(Unknown Source)
at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:1028)
at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:961)
at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:391)
at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:376)
at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:370)
at weblogic.servlet.internal.session.ReplicatedSessionData.(ReplicatedSessionData.java:97)
at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:292)
at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:2614)
at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:2251)
at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:260)

could anyone here help me out?

[Purushoth Thambu]

The exception says WebApp is not found on the secondary server. You can follow couple of debug steps to find out the issue.

- Try to hit the secondary server directly without going through the cluster.
- You can turn on the cluster servlet or proxy plugin debug flag and then use __WebLogicBridgeConfig debug parameter to get the cluster information.
- In addition you can set Replication debug flags:
DebugCluster,
DebugClusterAnnouncements,
DebugFailOver,
DebugReplication,
DebugReplicationDetails.

The above flags will log information in the log file about various cluster activity.