activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [5/6] activemq-artemis git commit: Adding chapter about UDP troubleshooting
Date Wed, 02 Sep 2015 14:23:12 GMT
Adding chapter about UDP troubleshooting

This is mostly importing some information that used to exist on old docs


Branch: refs/heads/master
Commit: 2cf0bb71c412504b42405bc918405b8af54f4412
Parents: fa15b29
Author: Clebert Suconic <>
Authored: Tue Sep 1 23:27:34 2015 -0400
Committer: Clebert Suconic <>
Committed: Wed Sep 2 10:21:33 2015 -0400

 docs/user-manual/en/     |  2 +-
 docs/user-manual/en/ | 19 +++++++++++++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/docs/user-manual/en/ b/docs/user-manual/en/
index 923b905..1bb6552 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -54,6 +54,6 @@
 * [Protocols and Interoperability](
 * [Tools](
 * [Maven Plugin](
-* [Performance Tuning](
+* [Troubleshooting and Performance Tuning](
 * [Configuration Reference](
diff --git a/docs/user-manual/en/ b/docs/user-manual/en/
index b9de082..beb387b 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -250,4 +250,23 @@ tunings won't apply to JDKs from other providers (e.g. IBM or JRockit)
     yourself do you really need MDBs? Can you accomplish the same task
     using just a normal message consumer?
+## Troubleshooting
+### UDP not working
+In certain situations UDP used on discovery may not work. Typical situations are:
+1. The nodes are behind a firewall. If your nodes are on different machines then it is possible
that the firewall is blocking the multicasts. you can test this by disabling the firewall
for each node or adding the appropriate rules.
+2. You are using a home network or are behind a gateway. Typically home networks will redirect
any UDP traffic to the Internet Service Provider which is then either dropped by the ISP or
just lost. To fix this you will need to add a route to the firewall/gateway that will redirect
any multicast traffic back on to the local network instead.
+3. All the nodes are in one machine. If this is the case then it is a similar problem to
point 2 and the same solution should fix it. Alternatively you could add a multicast route
to the loopback interface. On linux the command would be:
+# you should run this as root
+route add -net netmask dev lo
+ This will redirect any traffic directed to the to the loopback interface. This
will also work if you have no network at all.
+   * on Mac OS X, the command is slightly different:
+sudo route add -netmask

View raw message