You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@tomee.apache.org by bu...@apache.org on 2013/01/09 10:13:19 UTC
svn commit: r845700 - in /websites/staging/openejb/trunk: cgi-bin/ content/
content/documentation.html content/ejb-failover.html content/ejb-refs.html
content/multipulse-discovery.html
Author: buildbot
Date: Wed Jan 9 09:13:19 2013
New Revision: 845700
Log:
Staging update by buildbot for openejb
Modified:
websites/staging/openejb/trunk/cgi-bin/ (props changed)
websites/staging/openejb/trunk/content/ (props changed)
websites/staging/openejb/trunk/content/documentation.html
websites/staging/openejb/trunk/content/ejb-failover.html
websites/staging/openejb/trunk/content/ejb-refs.html
websites/staging/openejb/trunk/content/multipulse-discovery.html
Propchange: websites/staging/openejb/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 9 09:13:19 2013
@@ -1 +1 @@
-1429735
+1430739
Propchange: websites/staging/openejb/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 9 09:13:19 2013
@@ -1 +1 @@
-1429735
+1430739
Modified: websites/staging/openejb/trunk/content/documentation.html
==============================================================================
--- websites/staging/openejb/trunk/content/documentation.html (original)
+++ websites/staging/openejb/trunk/content/documentation.html Wed Jan 9 09:13:19 2013
@@ -205,6 +205,7 @@
<ul>
<li><a href="ejb-failover.html">Overview</a></li>
<li><a href="multicast-discovery.html">Multicast Discovery (UDP)</a></li>
+<li><a href="multipulse-discovery.html">Multipulse Discovery (UDP)</a></li>
<li><a href="multipoint-discovery.html">Multipoint Discovery (TCP)</a></li>
<li><a href="multipoint-considerations.html">Multipoint Considerations</a></li>
<li><a href="multipoint-recommendations.html">Multipoint Recommendations</a></li>
Modified: websites/staging/openejb/trunk/content/ejb-failover.html
==============================================================================
--- websites/staging/openejb/trunk/content/ejb-failover.html (original)
+++ websites/staging/openejb/trunk/content/ejb-failover.html Wed Jan 9 09:13:19 2013
@@ -220,6 +220,7 @@ group name.</p>
<ul>
<li><a href="multicast-discovery.html">Multicast UDP Discovery</a></li>
+<li><a href="multipulse-discovery.html">Multipulse UDP Discovery</a></li>
</ul>
<p>Multipoint</p>
Modified: websites/staging/openejb/trunk/content/ejb-refs.html
==============================================================================
--- websites/staging/openejb/trunk/content/ejb-refs.html (original)
+++ websites/staging/openejb/trunk/content/ejb-refs.html Wed Jan 9 09:13:19 2013
@@ -317,6 +317,7 @@ the scenes using server discovery logic
<ul>
<li><a href="multicast-discovery.html">Multicast Discovery (UDP)</a></li>
+<li><a href="multipulse-discovery.html">Multipulse Discovery (TCP)</a></li>
<li><a href="multipoint-discovery.html">Multipoint Discovery (TCP)</a></li>
</ul>
Modified: websites/staging/openejb/trunk/content/multipulse-discovery.html
==============================================================================
--- websites/staging/openejb/trunk/content/multipulse-discovery.html (original)
+++ websites/staging/openejb/trunk/content/multipulse-discovery.html Wed Jan 9 09:13:19 2013
@@ -149,12 +149,15 @@
<p>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.</p>
+is then sent. Multicast network traffic is effectively reduced to an absolute minimum.</p>
+
+<p>MultiPulse is only useful in network scenarios where both client and server can be
+configured to send multicast UDP packets.</p>
<h1>Server Configuration</h1>
-<p>When you boot the server there should be a <code>conf/conf.d/multipulse.properties</code> file
-containing:</p>
+<p>After you boot the server for the first time the default configuration will create the
+file <code>conf/conf.d/multipulse.properties</code> containing:</p>
<pre><code>server = org.apache.openejb.server.discovery.MulticastPulseAgent
bind = 239.255.2.3
@@ -164,19 +167,19 @@ group = default
</code></pre>
<p>You just need to enable the agent by setting <code>disabled = false</code>. 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. </p>
+disable multicast in the <code>multicast.properties file</code>, or at least to use a different
+bind address or port should you wish to use both.</p>
<p>All of the above settings except <code>server</code> can be modified as required.
The <code>port</code> and <code>bind</code> must be valid for general multicast/udp network communication.</p>
-<p>The <code>group</code> setting can be changed to further group servers that may use
-the same multicast channel. As shown below the client also has a <code>group</code>
-setting which can be used to select an appropriate server from the
-multicast channel.</p>
+<p>The <code>group</code> 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 <code>group</code>
+setting which can be used to select an appropriate server cluster from the multicast
+channel (See MultiPulse Client).</p>
<p>The next step is to ensure that the advertised services are configured for discovery.
-Edit the <code>ejbd.properties</code> file (and any other enabled services such as http, etc.) and
+Edit the <code>ejbd.properties</code> file (and any other enabled services such as http, etc.) and
ensure that the <code>discovery</code> option is set to a value that remote clients will be able
to resolve.</p>
@@ -188,10 +191,12 @@ threads = 20
discovery = ejb:ejbd://{bind}:{port}
</code></pre>
-<p>NOTE: If either <code>0.0.0.0</code> (IPv4) or <code>[::]</code> (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 <code>localhost</code> is used
-then only clients on the same machine will actually 'see' the server.</p>
+<p>NOTE: If either <code>0.0.0.0</code> (IPv4) or <code>[::]</code> (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.</p>
+
+<p>If <code>localhost</code> is used then only clients on the same physical machine will actually 'see' the
+server response.</p>
<h1>MultiPulse Client</h1>