• Post Reply Bookmark Topic Watch Topic
  • New Topic

executable jar files  RSS feed

 
Christopher Arthur
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've made two executable jar files. One runs with a double click and one fails to run. Both run from the command line. The important one is the one that fails. I have no clue where to start to figure out how to make it work.

"Java Virtual Machine Launcher: Fatal Exception Occurred. Program will exit."

How do I even begin to debug this?
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How are you running them from the command prompt? With java or javaw?

When double-clicking, if you're on a Windows system, it's likely configured to use javaw.

What happens when trying to run it from the command prompt with javaw?

Did you try the suggestion from your previous post on this problem?
 
Christopher Arthur
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It runs from the command line with java and with javaw just fine. I checked the way that executable .jars are configured in my registry and that seems to be ok. I looked into using "one-jar" software, but I decided against it for a few reasons. Mainly, it was easy enough just to repackage one single jar--I really don't need multiple jars for this project yet but if it gets bigger then maybe. The other reason is that I didn't want to tack on yet another open-source license that is different from the Apache 2.0 that I'm already under--I'm afraid to get my simple little program buried in legalities.

I wish that there was a way to turn on the profiler or the console from the double-click start...

Christopher Arthur
 
Christopher Arthur
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ah...I think I figured it out. I think it had to do with with JVM the javaw was configured to draw from. It shouldn't matter, but I think that it did because I had placed a .dll in the libs directory of one and not the other, and the program was looking for the .dll. Now it seems to work fine.
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Glad to hear it. Thanks for sharing what you learned.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!