Problems with running multiple EPP 4.3 instances
Issue
-
We are running into issues which appear to have been caused by multiple JBoss servers updating the same schema at similar times. When multiple updates happened in a short amount of time (ie. more than one a minute) the active portal seemed to become inconsistent with the database. Symptoms of this included pages appearing in portal admin that throw an exception when clicked on and pages not appearing in the portal site at all.
After 30 minutes (hibernate eh cache timeout appears to be 30 minutes) the active portal would refresh from the database and the issue seems to disappear.
Would clustering the JBoss portal servers prevent this issue? -
Currently, in a production environment, we have a Portal web farm but if we update the Portal content from one of the servers the rest of the Portal servers do not show the latest information.
The portal content is stored inside the CMS using the PortalDS database so we guess this is a problem with hibernate cache.
We are not using session replication because is not a requirement. If the user lost their connection with one Portal Webserver he/she has to reconnect again but we must guarantee that all people are watching the same latest information
Environment
- JBoss Enterprise Portal Platform (EPP)
- 4.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.