Stack trace contains nothing that indicates where the exception originates

0
We are seeing logged errors with extensive stack traces such as:   2024-07-31 07:32:48.610 ERROR - Connector: null com.mendix.systemwideinterfaces.MendixRuntimeException: org.eclipse.jetty.io.EofException: Closed at com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:23) Caused by: org.eclipse.jetty.io.EofException: Closed at org.eclipse.jetty.server.HttpOutput.checkWritable(HttpOutput.java:756) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:780) at java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:233) at java.base/sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:337) at java.base/sun.nio.cs.StreamEncoder.close(StreamEncoder.java:161) etc - the stack trace goes on for some time, but its all java / scala / mendix namespaces - at no point do we get any link to the originating microflow or action. Is there some configuration we need to add to get this debug info ?  
asked
1 answers
0

Hey,

 

Is this the top error? If you are you getting simultaneous errors, normally the top one is the one that specifies the error location in app.

 

 

Best,

Miguel Sabugueiro

answered