diff --git a/akka-docs/rst/general/supervision.rst b/akka-docs/rst/general/supervision.rst index 3c65ae44d8..15d5c610ae 100644 --- a/akka-docs/rst/general/supervision.rst +++ b/akka-docs/rst/general/supervision.rst @@ -199,13 +199,6 @@ external resource, which may also be one of its own children. If a third party terminates a child by way of the ``system.stop(child)`` method or sending a :class:`PoisonPill`, the supervisor might well be affected. -.. warning:: - - DeathWatch for Akka Remote does not (yet) get triggered by connection failures – - which means that if the parent node or the network goes down, nobody will get notified. - This feature may be added in a future release of Akka Remoting. - Akka Cluster, however, has such functionality. - One-For-One Strategy vs. All-For-One Strategy --------------------------------------------- diff --git a/akka-docs/rst/intro/getting-started.rst b/akka-docs/rst/intro/getting-started.rst index 5d14a962e0..6b8f87a3b4 100644 --- a/akka-docs/rst/intro/getting-started.rst +++ b/akka-docs/rst/intro/getting-started.rst @@ -227,6 +227,15 @@ Using Akka with NetBeans Setup SBT project and then use `sbt-netbeans-plugin `_ to generate a NetBeans project. +Do not use -optimize Scala compiler flag +---------------------------------------- + +.. warning:: + + Akka has not been compiled or tested with -optimize Scala compiler flag. + Strange behavior has been reported by users that have tried it. + + Build from sources ------------------ diff --git a/akka-docs/rst/java/zeromq.rst b/akka-docs/rst/java/zeromq.rst index e026e7bbe4..c598211de1 100644 --- a/akka-docs/rst/java/zeromq.rst +++ b/akka-docs/rst/java/zeromq.rst @@ -13,7 +13,7 @@ ZeroMQ is very opinionated when it comes to multi-threading so configuration opt The ZeroMQ module for Akka is written against an API introduced in JZMQ, which uses JNI to interact with the native ZeroMQ library. Instead of using JZMQ, the module uses ZeroMQ binding for Scala that uses the native ZeroMQ library through JNA. In other words, the only native library that this module requires is the native ZeroMQ library. The benefit of the scala library is that you don't need to compile and manage native dependencies at the cost of some runtime performance. The scala-bindings are compatible with the JNI bindings so they are a drop-in replacement, in case you really need to get that extra bit of performance out. -.. info:: +.. note:: The currently used version of ``zeromq-scala-bindings`` is only compatible with zeromq 2; zeromq 3 is not supported. diff --git a/akka-docs/rst/scala/zeromq.rst b/akka-docs/rst/scala/zeromq.rst index 2984f26b85..272862a422 100644 --- a/akka-docs/rst/scala/zeromq.rst +++ b/akka-docs/rst/scala/zeromq.rst @@ -13,7 +13,7 @@ ZeroMQ is very opinionated when it comes to multi-threading so configuration opt The ZeroMQ module for Akka is written against an API introduced in JZMQ, which uses JNI to interact with the native ZeroMQ library. Instead of using JZMQ, the module uses ZeroMQ binding for Scala that uses the native ZeroMQ library through JNA. In other words, the only native library that this module requires is the native ZeroMQ library. The benefit of the scala library is that you don't need to compile and manage native dependencies at the cost of some runtime performance. The scala-bindings are compatible with the JNI bindings so they are a drop-in replacement, in case you really need to get that extra bit of performance out. -.. info:: +.. note:: The currently used version of ``zeromq-scala-bindings`` is only compatible with zeromq 2; zeromq 3 is not supported.