因为'Akka.jvm-exit-on-fatal-error'为ActorSystem [mpe]启用而关闭JVM java.lang.StackOverflowError：null

Question

我正在开发一个需要接受小于1,00,000阈值的SOAP XML请求的修复程序。这样我们就可以在处理之前验证大型xml文档。

现在，当阈值小于1,00,000时，我对akka的错误报告感到困惑。我注意到如果一个父级下的元素超过2000，我就会收到此错误。如果元素被多个父元素划分，我们就不会得到错误。请帮我弄清楚akka的错误。

I have also to tried with disabling "akka.jvm-exit-on-fatal-error" in the configuration.

akka {

  jvm-exit-on-fatal-error = off

  actor {
    provider = "akka.remote.RemoteActorRefProvider"
  }

  remote {
    enabled-transports = ["akka.remote.netty.ssl"] 
    .
    .
    .
  }
} 

Example of Soap Request Body:

<soapenv:Body>
    <cai3:Create>
        <cai3:Attributes>
            <CreateAttributes attributeId="1">
                <attributeId>12345678</attributeId>
                <!--Zero or more repetitions:-->
                <node1 attributeId="12345678">
                    <node1>12345678</node1>
                    <node1/>
                </node1> 
                .......
                .......
                .......
                .......
                .......
                .......
                .......

                on so on upto 3000 same elements

                </CreateAttributes>
        </cai3:Attributes>
    </cai3:Create>
</soapenv:Body>

Exception Log

Module 2019-02-13 17:07:20,669+0800 [t-dispatcher-16] ERROR [akka.actor.ActorSystemImpl] Uncaught error from thread [mpe-akka.remote.default-remote-dispatcher-6]: null, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[mpe]
java.lang.StackOverflowError: null
        at java.lang.Exception.<init>(Exception.java:76) [na:1.8.0_172]
        at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89) [na:1.8.0_172]
        at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) [na:1.8.0_172]
        at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source) [na:na]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [na:1.8.0_172]
        at java.lang.reflect.Method.invoke(Method.java:498) [na:1.8.0_172]
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1128) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) [na:1.8.0_172]
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) [na:1.8.0_172]
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) [na:1.8.0_172]
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) [na:1.8.0_172]
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) [na:1.8.0_172]
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) [na:1.8.0_172]

Answer 1

看起来您通过akka-http消费SOAP消息时没有问题。

基于您发布的堆栈跟踪，问题在于导致java.lang.StackOverflowError的java序列化，并且它要么是因为您通过akka-remote，akka-cluster发送消息，要么您使用akka-persistence保留此消息。这些是可以在akka中使用java序列化的地方。除非你自己明确地使用它。

你可以阅读为什么JavaSerializationIsBroken并导致StackOverflowError错误。

我建议你尝试消费消费而不涉及akka-remote和akka-persistence。如果这确实有帮助，您知道问题出在java序列化上。

下一步将用更现代的序列化协议替换java序列化，如protocol-buffers。