Skip to main content

Java application opening then immediately closing on OSX

I have had several occasion's where Java apps would open, and then immediately close.  Often, I don't have the time to dig into the reason, as they aren't crucial.  So, I just move on. Recently, I was maddened by this happening to an application ( see other blog post on Kindle Previewer ) I really needed to use, so I had to get into the trench.  After cracking open the app, and rooting through the various files, I did some spot-checks of the java version used to build the jars ( 2 bytes at offsets 6 & 7 ), as well as had a look at the info.plist, which had the JVMVersion key set at 1.5+.

Since Oracle took over Java, Apple has essentially abandoned it to them, and hasn't done an update I *think* since version 6. All of Apple's Tooling for Java stops with JVMVersion key's of 6* and 6+.  The short answer to all this is, if something was built using Apple's AppBundler tools, and you have updated Java on your Mac to 7 or above, you're probably SOL to get the app to work.  The symptom is the app opening, and immediately closing.

You might think you could simply open info.plist, and change JVMVersion's value to 7*, 7+, or maybe 8*, or 8+.. but you'd be wrong.  One main factor that causes this is the location's of Java have changed from where Apple had it, and where Oracle now installs it.  Apple's software of course looks for things where Apple expects them to be.

There are a few things you can do.  Perhaps the simplest is to try setting:
version key's value to 1.6 (NOT 1.6+) in info.plist ( within the contents/macos folder of the app ).

A sure fix is to change the launcher script ( located inside the "contents" of the app, within the MACOS directory ), and add the following line at the top of the file, just under the "shebang": ( #!/bin/sh ):


export JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

The other is making use of java_home, a wonderful little tool that gives the Java Home location of the current JDK on stdout.  It's located:


/usr/libexec/java_home

You could make use of it, much like the hard-lined code snippet above, in scripts by executing something along the lines of:


export JAVA_HOME=`/usr/libexec/java_home`

This command has some options that are well worth having a look at.. this is a pretty handy little tool.

As an aside, another way of determining the version of Java that built a Jar is via the command-line's file command.  I don't know if it's 100%, but it should give good results.  First crack open the jar:


$ jar xf Wambamdoodle.jar

And then use file on one of the classes from within the Jar:


$ file ./org/wamzo/wambamdoodle/Apprehender.class

It will return something along the lines of:


./org/wamzo/wambamdoodle/Aprehender.class: compiled Java class data, version 50

The class version's major number corresponds to the following Java JDK versions:

  • 46 = Java 1.2
  • 47 = Java 1.3
  • 48 = Java 1.4
  • 49 = Java 5
  • 50 = Java 6
  • 51 = Java 7
  • 52 = Java 8

Labels:
Location: Portland, OR, USA

Comments

Post a Comment

Popular posts from this blog

Codeigniter vs. Kohana Database access speeds

I was doing some basic profiling for a project in which I needed the fastest raw speed I could get with database queries. I'm a fan of Codeigniter for projects that are suitable for it, but had heard from some that Kohana was faster, so I decided to do a very basic comparison of the two. I was using MAMP for OSX, and created a very small db, with a table that had 3 fields: (id), (first), and (last). The data sample was also very small, only a few records. The basic query I tested was a "SELECT * FROM [table]". There is of course nothing remotely scientific about this. It was just a quick ad dirty, very limited comparison. Take it as such. Versions used: CI2.1.3, Kohana 3.3.0. Codeigniter I really like Codeigniter (CI). But, one thing that is very evident from their own profiling functions, is that CI is a bit of a memory hog! Essentially, the same Controller function running in CI takes approximately 10X more memory than in Kohana! This in itself is not ...
Post a Comment
Read more

Passing Functions and Lambdas into Functions with Ruby

Ruby's New Style of Lambda Functions f = ->( m ) { p m } f.call( 1 ) #=> 1 Which of course means the same thing as: f = lambda { |n| p n } f.call(1) #=> 1 Ruby Proc Objects p = Proc.new { |n| p n + 2 } p.call(2) #=> 4 Using a Function as a Closure in Ruby def domo( k ) ->(m) { p m + k } end z = domo( 5 ) z.call( 5 ) #=> 10 Function :domo takes a single parameter. Within :domo , we create a lambda that takes a single parameter, and adds that parameter to the value :domo takes in as its parameter. Then, we assign z to be the result of the lambda in :domo with its 'k' parameter loaded with 5. When z is called, we pass (another) 5 to it. This parameter loads the lambdas n parameter. The lambda executes, essentially adding n (5) + k (5) and yielding the result of 10. The thing about closures such as this is, we can load the initial value of the lambda to be whatever we want it to be when assigning the function :domo '...
Post a Comment
Read more