[jira] [Resolved] (SPARK-1703) Warn users if Spark is run on JRE6 but compiled with JDK7

["Patrick Wendell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell resolved SPARK-1703.
------------------------------------

    Resolution: Fixed

Issue resolved by pull request 627
[https://github.com/apache/spark/pull/627]

> Warn users if Spark is run on JRE6 but compiled with JDK7
> ---------------------------------------------------------
>
>                 Key: SPARK-1703
>                 URL: https://issues.apache.org/jira/browse/SPARK-1703
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: Patrick Wendell
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> Right now since the JRE silently swallows the invalid jar, it will produce really confusing behavior if users hit this. We should check if we are in this situation (either in spark-class or compute-classpath) and fail with an explicit error.
> We can do something like:
> {code}
> $JAVA_HOME/bin/jar -tf lib/spark-assembly-1.0.0-SNAPSHOT-hadoop1.0.4.jar org/apache/spark/SparkContext
> {code}
> Which, when a user is running with JRE 6 and a JDK-7-compiled jar will produce:
> {code}
> java.util.zip.ZipException: invalid CEN header (bad signature)
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:132)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:93)
> 	at sun.tools.jar.Main.list(Main.java:997)
> 	at sun.tools.jar.Main.run(Main.java:242)
> 	at sun.tools.jar.Main.main(Main.java:1167)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)