This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, We are having WebSphere 4.0.2 running on AIX with following configuration - Two AIX box having two clones per box. - Persistant Session with: Write frequency = End of service method Write Contents = Only Updated attributes In our application we set 5K serializable object in session which is keep on updated with each request. But during failover sometime I am finding that object does not have latest information i.e. it is out of sync between clones/node. Here is the sequnce of setting this object - First time we create the session and set that object in session using setAttribute() method - Now during subsequnce request we always get that object from session request.getAttibute("obj") and then update that object but we do not set back into session i.e. we do no issue setAttribute()again. Now my question is that whether it is required to do setAttribute() again, my understanding is that because of reference it is not required but sometime i am seeing that this object is not upto date. Thanks in advance. SK