Multicast listener join-timeout-milliseconds docs are incorrect?

Question

Hi,
I was attempting to make my local development startup faster by doing this in my tangosol-coherence-override.xml file:
<multicast-listener>
<join-timeout-milliseconds>1</join-timeout-milliseconds>
</multicast-listener>
Basically, I want to disable multicast, but since that's not currently possible, setting it to the quickest timeout seems the best way to accomplish that. We use well-known-address lists and don't rely on multicast anyhow.
The docs here: [http://coherence.oracle.com/display/COH35UG/multicast-listener] seem to indicate it should be possible to set the value to 1, but at startup, I get this error:
2010-02-10 17:13:54,511 INFO [C3P0Registry.java:204] Initializing c3p0-0.9.1.2 [built 21-May-2007 15:04:56; debug? true; trace: 10]
2010-02-10 17:13:54.970/41.077 Oracle Coherence GE 3.5.2/463p1 <Error> (thread=main, member=n/a): Error while starting cluster: java.lang.IllegalArgumentException: Value out of range [1000, 1000000]: 1
     at com.tangosol.coherence.component.net.ClusterConfig.checkRange(ClusterConfig.CDB:4)
     at com.tangosol.coherence.component.net.ClusterConfig.setClusterAnnounceTimeout(ClusterConfig.CDB:1)
     at com.tangosol.coherence.component.net.ClusterConfig.fromXml(ClusterConfig.CDB:46)
     at com.tangosol.coherence.component.net.Cluster.configure(Cluster.CDB:10)
(omitted many lines for brevity)
Setting to 1000 works and definitely speeds up startup during development, but setting it to 1 would be even better. Can the docs be updated, or maybe get a feature to disable multicast entirely?
Thanks,
Rob Roland
Shopzilla, Inc.

Answer 1

Hi Jonathan,
Thanks for your reply. We do that, but it still seems to perform multicast discovery.
My configuration looks like this:
<?xml version='1.0'?>
<coherence>
<!-- This configuration will start up Coherence locally.
To learn more about productionalizing Coherence,
see http://wiki.tangosol.com/display/COH33UG/Production+Checklist -->
<cluster-config>
<member-identity>
<cluster-name>localCluster1</cluster-name>
</member-identity>
<unicast-listener>
<well-known-addresses>
<socket-address id="1">
<address>localhost</address>
<port system-property="tangosol.coherence.localport">34500</port>
</socket-address>
</well-known-addresses>
<port system-property="tangosol.coherence.localport">34500</port>
<port-auto-adjust system-property="tangosol.coherence.localport.adjust">true</port-auto-adjust>
</unicast-listener>
<multicast-listener>
<join-timeout-milliseconds>1000</join-timeout-milliseconds>
</multicast-listener>
<packet-publisher>
<packet-delivery>
<timeout-milliseconds>60000</timeout-milliseconds>
</packet-delivery>
</packet-publisher>
</cluster-config>
<configurable-cache-factory-config>
<class-name system-property="tangosol.coherence.cachefactory">
com.tangosol.coherence.spring.SpringAwareCacheFactory
</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value system-property="tangosol.coherence.cacheconfig">cache-config.xml</param-value>
</init-param>
<init-param id="1">
<param-type>java.lang.String</param-type>
<param-value system-property="tangosol.coherence.springconfig">applicationContext.xml</param-value>
</init-param>
</init-params>
</configurable-cache-factory-config>
</coherence>
And I set the following System properties:
tangosol.coherence.distributed.localstorage=true
tangosol.coherence.override=tangosol-coherence-override-ci.xml
tangosol.coherence.localhost=localhost
tangosol.coherence.ttl=0
But I am still subjected to the pause for multicast discovery.