Hello, Our Jetspeed portal application is running on 2 servers, A & B. Application requests over HTTP are load-balanced between the 2 servers.
We have noticed unusual behavior if multiple browser sessions are opened for our application URL. For example, if I open 6 browser sessions and I am the only user in the system, I will invariably get 3 sessions running from server A and 3 running from server B. When I make portal changes in a browser that's running on server A, the changes are visible when I refresh the other 2 browser sessions running on server A. However, the changes are not visible in browsers running on the other server B even after refresh. Both these application server instances share the same Jetspeed database, so I suspect that caching on the Jetspeed level is responsible for the discrepancy between the 2 servers. If I leave the system for a day or so, the 2 servers become synchronized again and changes made previously on server A are propagated over to the instance on server B. This is not ideal because a delay in showing updated portal preferences would impact user experience. If it is a caching issue, how long before the cache expires by default? Can I reduce the lifetime of the cache or force a refresh? Kind Regards, Siofra -- View this message in context: http://www.nabble.com/Caching-in-Jetspeed-2.1.2-tp18753770p18753770.html Sent from the Jetspeed - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
