Author: andygumbrecht
Date: Wed Jan 9 09:12:24 2013
New Revision: 1430739
URL: http://svn.apache.org/viewvc?rev=1430739&view=rev
Log:
Multipulse discovery
Modified:
openejb/site/trunk/content/documentation.mdtext
openejb/site/trunk/content/ejb-failover.mdtext
openejb/site/trunk/content/ejb-refs.mdtext
openejb/site/trunk/content/multipulse-discovery.mdtext
Modified: openejb/site/trunk/content/documentation.mdtext
URL:
http://svn.apache.org/viewvc/openejb/site/trunk/content/documentation.mdtext?rev=1430739&r1=1430738&r2=1430739&view=diff
==============================================================================
--- openejb/site/trunk/content/documentation.mdtext (original)
+++ openejb/site/trunk/content/documentation.mdtext Wed Jan 9 09:12:24 2013
@@ -60,6 +60,7 @@ See also the [examples page](examples-tr
### Discovery and Failover
- [Overview](ejb-failover.html)
- [Multicast Discovery (UDP)](multicast-discovery.html)
+- [Multipulse Discovery (UDP)](multipulse-discovery.html)
- [Multipoint Discovery (TCP)](multipoint-discovery.html)
- [Multipoint Considerations](multipoint-considerations.html)
- [Multipoint Recommendations](multipoint-recommendations.html)
Modified: openejb/site/trunk/content/ejb-failover.mdtext
URL:
http://svn.apache.org/viewvc/openejb/site/trunk/content/ejb-failover.mdtext?rev=1430739&r1=1430738&r2=1430739&view=diff
==============================================================================
--- openejb/site/trunk/content/ejb-failover.mdtext (original)
+++ openejb/site/trunk/content/ejb-failover.mdtext Wed Jan 9 09:12:24 2013
@@ -72,6 +72,7 @@ group name.
Multicast
- [Multicast UDP Discovery](multicast-discovery.html)
+ - [Multipulse UDP Discovery](multipulse-discovery.html)
Multipoint
Modified: openejb/site/trunk/content/ejb-refs.mdtext
URL:
http://svn.apache.org/viewvc/openejb/site/trunk/content/ejb-refs.mdtext?rev=1430739&r1=1430738&r2=1430739&view=diff
==============================================================================
--- openejb/site/trunk/content/ejb-refs.mdtext (original)
+++ openejb/site/trunk/content/ejb-refs.mdtext Wed Jan 9 09:12:24 2013
@@ -170,4 +170,5 @@ This sort of arangement can also happen
the scenes using server discovery logic that can function on either UDP or
TCP. See these docs for more details on Failover and Discovery:
- [Multicast Discovery (UDP)](multicast-discovery.html)
+ - [Multipulse Discovery (TCP)](multipulse-discovery.html)
- [Multipoint Discovery (TCP)](multipoint-discovery.html)
Modified: openejb/site/trunk/content/multipulse-discovery.mdtext
URL:
http://svn.apache.org/viewvc/openejb/site/trunk/content/multipulse-discovery.mdtext?rev=1430739&r1=1430738&r2=1430739&view=diff
==============================================================================
--- openejb/site/trunk/content/multipulse-discovery.mdtext (original)
+++ openejb/site/trunk/content/multipulse-discovery.mdtext Wed Jan 9 09:12:24
2013
@@ -2,47 +2,52 @@ Title: MultiPulse (UDP) Discovery
MultiPulse is an alternative multicast lookup that does not use a regular
heartbeat.
Instead, servers listen for a multicast request packet (a pulse) to which a
response
-is sent. Multicast network traffic is effectively reduced to an absolute
minimum.
+is then sent. Multicast network traffic is effectively reduced to an absolute
minimum.
+
+MultiPulse is only useful in network scenarios where both client and server
can be
+configured to send multicast UDP packets.
# Server Configuration
-When you boot the server there should be a `conf/conf.d/multipulse.properties`
file
-containing:
+After you boot the server for the first time the default configuration will
create the
+file `conf/conf.d/multipulse.properties` containing:
- server = org.apache.openejb.server.discovery.MulticastPulseAgent
- bind = 239.255.2.3
- port = 6142
+ server = org.apache.openejb.server.discovery.MulticastPulseAgent
+ bind = 239.255.2.3
+ port = 6142
disabled = true
- group = default
+ group = default
You just need to enable the agent by setting `disabled = false`. It is
advisable to
-disable multicast in the multicast.properties file, or at least to use a
different
-bind address or port should you wish to use both.
+disable multicast in the `multicast.properties file`, or at least to use a
different
+bind address or port should you wish to use both.
All of the above settings except `server` can be modified as required.
The `port` and `bind` must be valid for general multicast/udp network
communication.
-The `group` setting can be changed to further group servers that may use
-the same multicast channel. As shown below the client also has a `group`
-setting which can be used to select an appropriate server from the
-multicast channel.
+The `group` setting can be changed to further group/cluster servers that may
use
+the same multicast channel. As shown below the client also has an optional
`group`
+setting which can be used to select an appropriate server cluster from the
multicast
+channel (See MultiPulse Client).
The next step is to ensure that the advertised services are configured for
discovery.
-Edit the `ejbd.properties` file (and any other enabled services such as http,
etc.) and
+Edit the `ejbd.properties` file (and any other enabled services such as http,
etc.) and
ensure that the `discovery` option is set to a value that remote clients will
be able
to resolve.
- server = org.apache.openejb.server.ejbd.EjbServer
- bind = 0.0.0.0
- port = 4201
- disabled = false
- threads = 20
- discovery = ejb:ejbd://{bind}:{port}
-
-NOTE: If either `0.0.0.0` (IPv4) or `[::]` (IPv6) wildcard addresses are used
then the server
-will actually broadcast all of it's known public hosts to clients. Clients
will then cycle
-though and attempt to connect to the provided hosts until successful. If
`localhost` is used
-then only clients on the same machine will actually 'see' the server.
+ server = org.apache.openejb.server.ejbd.EjbServer
+ bind = 0.0.0.0
+ port = 4201
+ disabled = false
+ threads = 20
+ discovery = ejb:ejbd://{bind}:{port}
+
+NOTE: If either `0.0.0.0` (IPv4) or `[::]` (IPv6) wildcard bind addresses are
used then the
+server will actually broadcast all of it's known public hosts to clients.
Clients will then
+cycle though and attempt to connect to the provided hosts until successful.
+
+If `localhost` is used then only clients on the same physical machine will
actually 'see' the
+server response.
# MultiPulse Client
