Hello Everyone, 
  
   We are a JBOSS shop currently using JBOSS 3.2.6 and using the JBOSSCache 
version that comes with 3.2.6 to store the session information for the user (we 
are not using Tomcat so we have our own session tracking solution using a 
specially configured JBossCache). We are in production for a large .com site 
and overall things have been running well. However, there is an issue 
preventing us from successfully running the JBossCache in a cluster: 

   1. When we need to restart a node on the cluster we have set 
FetchStateOnStartup to true and set the InitialStateRetrievalTimeout to 120000 
milliseconds. Keeping in mind that this is a REPL_SYNC cache on the cluster, 
the problem is that --on restart-- once the timeout is hit the cache appears to 
quit replicating and as such the restarted node has an incomplete copy of the 
cache. Does anyone know how to force the cache to finish replication on startup 
so we can be guaranteed that we have a duplicate of the cache on every node in 
our cluster? 

Thanks in advance for your time and consideration,

Dan 


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862600#3862600

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862600


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to