Yes I just saw that. That clearly is a bug - since the <clustering> tag should
imply some form of non-local clustering. And I thought the default was DIST_SYNC. But I
wonder how we'd deal with that now, since by changing the default we may end up
breaking existing cfg files. It is even documented as a default of LOCAL.
http://docs.jboss.org/infinispan/4.1/apidocs/config.html#ce_default_clust...
On a side note, the config validator needs more detail as well. E.g., defining a repl
queue for a cluster mode of DIST should not be allowed. I'll create a JIRA for this.
On 22 Oct 2010, at 10:59, Galder Zamarreño wrote:
The following named cache configuration:
<namedCache name="withReplicatinQueue">
<clustering>
<async useReplQueue="true" replQueueInterval="100"
replQueueMaxElements="200"/>
</clustering>
</namedCache>
Is considered to be a local cache. Should that really be the case? This is taken from
all.xml.
The result is that replication queue obviously won't be used.
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org