[
https://issues.apache.org/jira/browse/OPENEJB-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294216#comment-13294216
]
Andy Gumbrecht commented on OPENEJB-1838:
-----------------------------------------
The idea / motivation behind this feature is to create a discovery option where
multicast traffic is kept to an absolute minimum and to considerably reduce
discovery times. In environments where multiple multicast configured servers
are running within the same network multicast traffic can also become extremely
noisy.
Currently a server is configured with a regular 'heartbeat' that clients must
listen for. A client must listen for an at least estimated amount of time in
order to catch heartbeats of all available servers. This amount of time is
defined by the server and is at least the time of one heartbeat plus an
arbitrary amount. To reduce this time the only option is increase the heartbeat
rate, which in turn increases multicast traffic.
> Add 'MultiPulse' discovery - An alternative multicast discovery option
> ----------------------------------------------------------------------
>
> Key: OPENEJB-1838
> URL: https://issues.apache.org/jira/browse/OPENEJB-1838
> Project: OpenEJB
> Issue Type: Improvement
> Components: server
> Affects Versions: (not version related)
> Environment: All
> Reporter: Andy Gumbrecht
> Assignee: Andy Gumbrecht
> Priority: Trivial
> Labels: MultiPulse, Multicast
> Fix For: (trunk/openejb)
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Add a multicast discovery feature that does not require a constant heartbeat.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
