You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geaflow.apache.org by "johntomcat7408-cmyk (via GitHub)" <gi...@apache.org> on 2026/07/29 08:17:41 UTC

Re: [I] enhancement: Exception handling improvements [geaflow]

johntomcat7408-cmyk commented on issue #701:
URL: https://github.com/apache/geaflow/issues/701#issuecomment-5114957207

   While checking the JDK 11 CI log for #816, I noticed that the cluster tests intercept `System.exit()` through `SystemExitSignalCatcher`, but the expected exception escapes from the worker thread and is reported as an error:
   
   ```text
   Error: Exception in thread geaflow-exception-collect-0
   org.apache.geaflow.common.exception.GeaflowRuntimeException:
   org.apache.geaflow.common.exception.GeaflowRuntimeException:
   throw exception instead of exit process
   
   Caused by: org.apache.geaflow.common.exception.GeaflowRuntimeException:
   throw exception instead of exit process
       at org.apache.geaflow.cluster.util.SystemExitSignalCatcher.checkExit(SystemExitSignalCatcher.java:46)
       at java.base/java.lang.System.exit(System.java:1769)
       at org.apache.geaflow.cluster.exception.ComponentExceptionSupervisor.process(ComponentExceptionSupervisor.java:45)
       at org.apache.geaflow.cluster.task.runner.AbstractTaskRunner.run(AbstractTaskRunner.java:48)
   ```
   
   CI log: https://github.com/apache/geaflow/actions/runs/30429273767/job/90507125902?pr=816
   
   This comes from existing cluster test behavior and is unrelated to the MongoDB connector changes in #816. The exception is expected to prevent the test JVM from exiting, but the uncaught stack trace makes the CI log look like a real failure.
   
   Would it make sense to handle this as a focused follow-up under this issue? I can work on a small change that keeps the exit behavior covered without leaking the expected exception into the CI log.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@geaflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@geaflow.apache.org
For additional commands, e-mail: issues-help@geaflow.apache.org