I think this is because of https://github.com/akka/akka/issues/22324
It was marked as in progress but it seems there never was a PR submitted to
fix that.
--
Johan
Akka Team
On Wed, Jun 7, 2017 at 12:16 PM, wrote:
> yes, *situation 1 *, the log has tell me the reason cause the error ,
> and i
If you set `akka.jvm-exit-on-fatal-error = on` it should log stack traces
in all cases to stderr.
Johannes
On Wed, Jun 7, 2017 at 12:16 PM, wrote:
> yes, *situation 1 *, the log has tell me the reason cause the error ,
> and i know how to solve *situation 1 * .
> but *situation 2,3,4 *, din't
yes, *situation 1 *, the log has tell me the reason cause the error , and
i know how to solve *situation 1 * .
but *situation 2,3,4 *, din't tell me the reason ( the stack ), id dont
hnow how solve this problem.
在 2017年6月7日星期三 UTC+8下午5:00:07，Johannes Rudolph写道：
>
>
> The rest of the stack here
The rest of the stack here will tell you where the problem comes from:
On Wed, Jun 7, 2017 at 10:40 AM, wrote:
> * situation 1 : ( has tell me the stack, and tell me *Shutdown finished *
> )*
> INFO | jvm 1| 2017/04/07 15:49:52 | java.lang.NoClassDefFoundError:
> Lws/protos/EnumsProtos$Har
thanks for your help,below is part of my app config .
akka {
jvm-exit-on-fatal-error = off
actor {
provider = "akka.cluster.ClusterActorRefProvider"
}
remote {
log-remote-lifecycle-events = off
enabled-transports = ["akka.remote.netty.tcp"]
netty.tcp {
port = 20300
Hi,
my colleague Arnout just found out that the error will only be logged to
stderr if you enable the `akka.jvm-exit-on-fatal-error` setting. Can you
try enabling this setting and then run again?
I also filed an issue to improve the logging of fatal
errors: https://github.com/akka/akka/issue
Hi,
in cases of fatal errors, the error and stack trace is logged to stderr
(not using the logging framework). Note that in some cases, the logging
itself may fail (that's why the error is fatal: after it happens, the state
of the JVM might be corrupted and operations like logging may fail for
