In trunk (4.6 snapshot at the time of writing) there is now the option to 'ignore' hosts in the multipulse.properties.
The original desire for MultiPulse was a virtually zero configuration for discovery of multi-homed systems. For example some of my server machines ship with up to 5 Ethernet cameras that use DHCP, a regular LAN and possibly several virtual IPs. MultiPulse pulses the entire discovered host list, and lets the client work out which hosts are good to go. The pulse actually goes out on all interfaces, so not even the server needs to 'know' it's LAN/bind address. However, if you are not lazy like me then you can modify the multipulse.properties file and add known unreachable hosts to the ignore parameter: ignore = [2002:5eba:a72a:0:f560:dda3:93ba:f7e5],SPECTRUM-SRV The client will then (based upon the previously discovered list) only try to connect to 10.0.1.7 - This is actually not going to improve performance here because it was already first in the list. A MultiPulse client will return the first reachable connection. You get the idea though. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/slow-multicast-discovery-can-be-optimized-by-caching-server-tp4660726p4661008.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
