I am a developer on a project that is being forced to use a load balancing server envirnment. The problem is that I am using a session attribute, UserObject, to keep track of user info. When the user logs in, a UserObject is created and before any action is executed the UserObject is check to be valid or not. If it is then it executes normal, if the object is invalid then the user is forwarded to the login page. The problem arrises when the controller switched the user from one server to the other, the session object is lost and thus the user is kicked out to the login page only for the same thing to happen again. What needs to be changed in the Sun One Configuration?
Somehow you need to make in-memory session replication work. In tomcat this is very easy. You'll have to check out sun's website to see how iplanet 6 does that. Or you could have a specific directory that you save your session info and then have all the servers access the session data from that one place. But the best bet is the in-memory session replication.