[
https://issues.apache.org/jira/browse/JOSHUA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446080#comment-15446080
]
Kellen Sunderland commented on JOSHUA-285:
------------------------------------------
This is fixed in PR https://github.com/apache/incubator-joshua/pull/45 . Any
uncaught exception will now be propagated from the threadpool thread that it
occurs on, back to the main thread that is iterating over translation results.
The main thread can have control over how to handle these failures, but they
will likely be fatal. In the case of the CLI tool for example we can just
crash with a stack trace.
There's also a test specifically causing a runtime exception on a worker thread
and ensuring that it propagates to the main response thread.
> Not all RuntimeExceptions are caught
> ------------------------------------
>
> Key: JOSHUA-285
> URL: https://issues.apache.org/jira/browse/JOSHUA-285
> Project: Joshua
> Issue Type: Bug
> Reporter: Matt Post
> Assignee: Kellen Sunderland
> Fix For: 6.1
>
>
> In many instances Joshua threads will throw a RuntimeException that is not
> caught, causing the decoder to hang indefinitely. These should be caught and,
> if serious enough, cause the decoder to die. An example of an error that is
> caught is running out of memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
