[jboss-user] [JBossCache] - Re: Replication Problem When Nodes Have Gone Away

bstansberry@jboss.com do-not-reply at jboss.com
Mon Sep 25 17:09:52 EDT 2006


Suggest you have a look at http://wiki.jboss.org/wiki/Wiki.jsp?page=FDVersusFD_SOCK, particularly the last bit.

I suspect the reason it's taking a long time to get the 2nd notification is that your code that handles the first notification is blocking the JGroups thread that sends up view change notifications.  If you're not doing this, when you get a view change notification, spawn a thread and do your puts into the cache in that thread.

Also, beginning in 1.3.0, JBC introduced a new class org.jboss.cache.config.Option, which can be passed to overloaded versions of the main api calls (e.g. get, put, remove).  You can create an Option with property "cacheModeLocal" set to "true"; if you pass that to a put or remove, the call will not replicate.  See the Option class javadocs for more.

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

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



More information about the jboss-user mailing list