* Log a warning if 'akka.remote.log-frame-size-exceeding' contains a bad value Currently, if 'akka.remote.log-frame-size-exceeding' is accidentally set to an invalid value (e.g. 'on') the developer does not get warned but remote communication fails with a not-very-helpful error message: ``` [INFO] [06/29/2018 15:07:41.657] [run-main-0] [akka.remote.Remoting] Starting remoting [INFO] [06/29/2018 15:07:41.847] [run-main-0] [akka.remote.Remoting] Remoting started; listening on addresses :[akka.tcp://akkaremotenull@localhost:2553] [INFO] [06/29/2018 15:07:41.849] [run-main-0] [akka.remote.Remoting] Remoting now listens on addresses: [akka.tcp://akkaremotenull@localhost:2553] [WARN] [06/29/2018 15:07:41.986] [akkaremotenull-akka.remote.default-remote-dispatcher-5] [akka.tcp://akkaremotenull@localhost:2553/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fakkaremotenull%40localhost%3A2552-0] Association with remote system [akka.tcp://akkaremotenull@localhost:2552] has failed, address is now gated for [5000] ms. Reason: [akka://akkaremotenull/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fakkaremotenull%40localhost%3A2552-0/endpointWriter: exception during creation] Caused by: [null] [INFO] [06/29/2018 15:07:41.993] [akkaremotenull-akka.actor.default-dispatcher-3] [akka://akkaremotenull/deadLetters] Message [io.ino.akkaremotenull.Greeter$Greet] from Actor[akka://akkaremotenull/temp/$a] to Actor[akka://akkaremotenull/deadLetters] was not delivered. [1] dead letters encountered. If this is not an expected behavior, then [Actor[akka://akkaremotenull/deadLetters]] may have terminated unexpectedly, This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'. ``` This commit fixes the issue by a) printing a warning message and b) ignoring the config setting. * Adress review comments Allows value 'off' for 'akka.remote.log-frame-size-exceeding' to be more tolerant and now logs the original error message of the ConfigException caught when parsing an invalid value: ``` [WARN] [07/05/2018 09:13:19.544] [akkaremotenull-akka.remote.default-remote-dispatcher-13] [RemoteMetricsOn(akka://akkaremotenull)] application.conf @ file:/Users/danbim/coding/akka-remote-null/target/scala-2.12/classes/application.conf: 19: Invalid value at 'akka.remote.log-frame-size-exceeding': No number in size-in-bytes value 'test'. For reference, check https://github.com/lightbend/config/blob/master/HOCON.md ``` * Check logFrameSizeExceeding against Int.MaxValue to allow JIT optimizations * Load 'akka.remote.log-frame-size-exceeding' in RemoteSettings |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| akka-actor/src/main | ||
| akka-actor-testkit-typed/src | ||
| akka-actor-tests/src/test | ||
| akka-actor-typed/src/main | ||
| akka-actor-typed-tests/src/test | ||
| akka-agent/src | ||
| akka-bench-jmh | ||
| akka-camel/src | ||
| akka-cluster | ||
| akka-cluster-metrics/src | ||
| akka-cluster-sharding/src | ||
| akka-cluster-sharding-typed/src | ||
| akka-cluster-tools/src | ||
| akka-cluster-typed/src | ||
| akka-contrib | ||
| akka-distributed-data/src | ||
| akka-docs/src | ||
| akka-multi-node-testkit/src/main | ||
| akka-osgi/src | ||
| akka-persistence/src | ||
| akka-persistence-query/src | ||
| akka-persistence-shared/src/test/scala/akka/persistence | ||
| akka-persistence-tck/src | ||
| akka-persistence-typed/src | ||
| akka-protobuf/src/main/java/akka/protobuf | ||
| akka-remote/src | ||
| akka-remote-tests/src | ||
| akka-slf4j/src | ||
| akka-ssl-config/src/main/scala/com/lightbend/sslconfig/akka | ||
| akka-stream/src/main | ||
| akka-stream-testkit/src | ||
| akka-stream-tests/src/test | ||
| akka-stream-tests-tck/src/test | ||
| akka-stream-typed/src | ||
| akka-testkit/src | ||
| project | ||
| scripts | ||
| src/main/ls | ||
| .gitignore | ||
| .java-version | ||
| .travis.yml | ||
| build.sbt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| COPYING.protobuf | ||
| LICENSE | ||
| README.md | ||
| RELEASING.md | ||
Akka 
We believe that writing correct concurrent & distributed, resilient and elastic applications is too hard. Most of the time it's because we are using the wrong tools and the wrong level of abstraction.
Akka is here to change that.
Using the Actor Model we raise the abstraction level and provide a better platform to build correct concurrent and scalable applications. This model is a perfect match for the principles laid out in the Reactive Manifesto.
For resilience, we adopt the "Let it crash" model which the telecom industry has used with great success to build applications that self-heal and systems that never stop.
Actors also provide the abstraction for transparent distribution and the basis for truly scalable and fault-tolerant applications.
Learn more at akka.io.
Reference Documentation
The reference documentation is available at doc.akka.io, for Scala and Java.
Community
You can join these groups and chats to discuss and ask Akka related questions:
- Forums: discuss.akka.io
- Chat room about using Akka:
- Issue tracker:
In addition to that, you may enjoy following:
- The news section of the page, which is updated whenever a new version is released
- The Akka Team Blog
- @akkateam on Twitter
- Questions tagged #akka on StackOverflow
- Projects built with Akka:
Contributing
Contributions are very welcome!
If you see an issue that you'd like to see fixed, the best way to make it happen is to help out by submitting a pull request implementing it.
Refer to the CONTRIBUTING.md file for more details about the workflow, and general hints on how to prepare your pull request. You can also ask for clarifications or guidance in GitHub issues directly, or in the akka/dev chat if a more real time communication would be of benefit.
A chat room is available for all questions related to developing and contributing to Akka:
License
Akka is Open Source and available under the Apache 2 License.