Hi,
I set up a simple tomcat cluster using the example from
http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html but using the
BackupManager.
I deployed a simple jsf portlet/app where you can store values in an
application scoped and a session scoped bean.
I access one server through a loadbalancer (haproxy) configured for sticky
sessions. When I store a value in the session bean I can see a session
being created in the manager/html/sessions for my app on both servers.
However if I shut down the current server and get directed to the other one
by the LB the session value is gone although I still continue using the
same JSESSIONID.
Any ideas for resolving that?
background info:
- Tomcat: bundled with Liferay 6.1. Tomcat version is 7.0.27.
- no SerializationException in the logs
- tested on Ubuntu VMs in VirtualBox and on real Win7 boxes connected via
router
- time is synced (both consoles show same time)
- no WARN or ERROR messages in the consoles
- app works fine while on one server
- <distributable/> tag is set in Liferay and my app
- tomcats notice when the other one dissappears
- in Liferay forums I was told it was a tomcat issue
- in the session there is an attribute (sessbean is my session bean,
cloudapp is my app):
* name: javax.portlet.p.cloudtest_WAR_cloudapp_LAYOUT_10639?sessbean
* value: [package of the bean].MySessionScopeBean@5394f184
I'm a newbie to this, so it might be something trivial (also since it's a
basic example).
Thanks for any advice!
