Wolf-Dieter Fink [http://community.jboss.org/people/wdfink] created the discussion "Re: Clustering an application that uses Spring singletons" To view the discussion, visit: http://community.jboss.org/message/571561#571561 -------------------------------------------------------------- What EJB version do you use 2.x or 3.x? It will help for an answer. Best try is to avoid such 'stateful' behaviour ;-( For our application (do not use spring) we found out that it will work without some caching more stable and without a performance drawback. We have entities with a high change frequency and the data in cache are ruled out and must be loaded anyhow. Solutions for you might be - JBoss(Tree)Cache, replicate the state in the cluster (time gap possible because of async replication after commit) - Special entity without caching or with the invalidation feature (EJB2 entities) - your own implementation and a signal if it must be refreshed (we do this for master data via JMS) Also you should think about the load-balancing, it is not ensured that two calls of SLSB in a sequence will reach the same JBoss instance in a cluster, this might produce problems if the cache-data will be not the same ... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/571561#571561] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolf-Dieter Fink [http://community.jboss.org/people/wdfink] created the discussion "Re: Clustering an application that uses Spring singletons" To view the discussion, visit: http://community.jboss.org/message/571581#571581 -------------------------------------------------------------- With EJB3 entities there is only a transactional caching (no 2nd level cache like EJB2). Are you sure that the caching will spare significant duration or cpu time ? A good principle will be 'only think about cache if you measure that it will bring benefit' -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/571581#571581] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolf-Dieter Fink [http://community.jboss.org/people/wdfink] created the discussion "Re: Clustering an application that uses Spring singletons" To view the discussion, visit: http://community.jboss.org/message/571639#571639 -------------------------------------------------------------- Ok, I understand the reason for the cache (was just food for thought) But another one ... If this data is loaded only once a day it might aceptable to load local on each cluster node at the same time, because if the time is in sync the difference is only a few seconds ... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/571639#571639] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolf-Dieter Fink [http://community.jboss.org/people/wdfink] created the discussion "Re: Clustering an application that uses Spring singletons" To view the discussion, visit: http://community.jboss.org/message/571760#571760 -------------------------------------------------------------- Also a solution. AFAIK the HA-singleton will start only once in a cluster (like JMS JBossMQ). In case of node crash there will be a gap al long as one other instance provide the service. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/571760#571760] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]