[
https://issues.apache.org/jira/browse/FLINK-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150823#comment-15150823
]
Aljoscha Krettek commented on FLINK-3438:
-----------------------------------------
It's good we have people running stuff with different locales... :D
I could not yet come up with a good solution. The problem is that the
ClassNotFoundException is thrown before our own code even runs in the external
process. So maybe there's nothing we can do about it except setting the locale
like you did in your workaround.
> ExternalProcessRunner fails to detect ClassNotFound exception because of
> locale settings
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-3438
> URL: https://issues.apache.org/jira/browse/FLINK-3438
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Stefano Baghino
> Priority: Minor
> Fix For: 1.0.0
>
>
> ExternalProcessRunner tries to detect a ClassNotFoundException in the run
> process by comparing its output with a fixed string of test; this means that
> localized text reporting said exception is not interpreted as such.
> To reproduce:
> * test the `ExternalProcessRunnerTest.testClassNotFound` setting the
> following system properties on the JVM: {{-Duser.country=IT
> -Duser.language=it}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
