Weblogic portal clustering

Question

Hi,
Help Please!
Now we need migrate an application to clustering environment. But there are some confusing scenario.
What we have done are:
1. make all objects in session serializable. For thoese unserializable, declare them as transient and take other workaround to assign value to them when accessed.
2. put up a clustering environment with two managed servers. Here we use IIS as frontend, and weblogic IIS plugin as cluster proxy. In proxy.ini file, we add WeblogicCluster paramter to specify managed server list.
3. add persistantStoreType/replicated session attribute to weblogic.xml
Then we code a simple application to test session replication. The application includes one pageflow. The pageflow has one class level variable and action form.
Now what confused us is the behavior of app upon clustering is not consistant. At the beginning, the session duplication seems works. So after re-setting the pageflow class level variable in a action, the pageflow instance seems duplicated to another managed server. So I stoped current one, and access another action to print out the variable. It works!
But after undeploying/redeploying the application serveral times, the session replication never works again. And each time, when printing out the variable value, it will be the initial value.
Question:
1. Is any other steps/special configuration needed to make clustering works?
2. Portal's pageflow instance is stored in session, is there any special coding criteria to follow to make pageflow instance replicatable?
3. Now in the managed servers and admin server's console, I never see such a debug log:
<i><Oct 9, 2003 12:38:21 PM PDT> <Debug> <Cluster> <000000>
<Created secondary for 5165892837402719733 on -7957889153726652135S:
192.168.11.112: [9001,9001, -1, -1,9001, -1, -1]: mydomain: MyServer-2></i>
as mentioned at http://wldj.sys-con.com/read/44435.htm
Thanks!
Best Regards
Weily

Answer 1

Hi,
Help Please!
Now we need migrate an application to clustering environment. But there are some confusing scenario.
What we have done are:
1. make all objects in session serializable. For thoese unserializable, declare them as transient and take other workaround to assign value to them when accessed.
2. put up a clustering environment with two managed servers. Here we use IIS as frontend, and weblogic IIS plugin as cluster proxy. In proxy.ini file, we add WeblogicCluster paramter to specify managed server list.
3. add persistantStoreType/replicated session attribute to weblogic.xml
Then we code a simple application to test session replication. The application includes one pageflow. The pageflow has one class level variable and action form.
Now what confused us is the behavior of app upon clustering is not consistant. At the beginning, the session duplication seems works. So after re-setting the pageflow class level variable in a action, the pageflow instance seems duplicated to another managed server. So I stoped current one, and access another action to print out the variable. It works!
But after undeploying/redeploying the application serveral times, the session replication never works again. And each time, when printing out the variable value, it will be the initial value.
Question:
1. Is any other steps/special configuration needed to make clustering works?
2. Portal's pageflow instance is stored in session, is there any special coding criteria to follow to make pageflow instance replicatable?
3. Now in the managed servers and admin server's console, I never see such a debug log:
<i><Oct 9, 2003 12:38:21 PM PDT> <Debug> <Cluster> <000000>
<Created secondary for 5165892837402719733 on -7957889153726652135S:
192.168.11.112: [9001,9001, -1, -1,9001, -1, -1]: mydomain: MyServer-2></i>
as mentioned at http://wldj.sys-con.com/read/44435.htm
Thanks!
Best Regards
Weily