Java Launch fails on second run: java.lang.NullPointerException

Question

I downloaded the .jnlp file and ran it. It runs fine. I close it and start it again, it runs fine.

However on the third try, it always throws java.lang.NullPointerException and the application will not launch.

If I restart the computer it works again. How can I fix this ?

java.lang.NullPointerException
    at com.sun.javaws.security.SigningInfo.overlapSigners(Unknown Source)
    at com.sun.javaws.security.SigningInfo.getCertificates(Unknown Source)
    at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
    at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.launch(Unknown Source)
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

I think your application is not terminating properly. When you close your application it still running. You can share your piece of code.. — Mohamed Saligh
– Mohamed Saligh, Commented Dec 8, 2010 at 2:08
program doesn't show up in task manager and neither does java.exe — KJW
– KJW, Commented Dec 8, 2010 at 2:14
I hate saying this, but, can you perhaps try to just reinstall the JRE and see if this persists? — Ryan Fernandes
– Ryan Fernandes, Commented Dec 8, 2010 at 3:18

Community · Accepted Answer · 2023-11-10 19:48:45Z

5

The stacktrace is the same as in Bug ID 6533653 and Bug ID 6850598. The root cause seems to be an empty JAR in JNLP. They said to have fixed it in Java 1.6 update 2 and Java 1.6 update 18 respectively.

However, there is a comment in the last bug which complains that the fix still doesn't work in 1.6 update 18, along with a description which look much like your situation:

In vm 6u18 this bug is NOT closed. You can launch your application once but after you have the following exception :
java.lang.NullPointerException

    at com.sun.javaws.security.SigningInfo.overlapSigners(Unknown Source)
    at com.sun.javaws.security.SigningInfo.getCertificates(Unknown Source)
    at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
    at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.launch(Unknown Source)
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

If I remove the empty jar from jnlp, all is ok. Please verify your correction before publication

So, try removing the empty JAR from the JNLP and report it to the JNLP authors as well.

edited Nov 10, 2023 at 19:48

CommunityBot

11 silver badge

answered Dec 8, 2010 at 3:23

BalusC

1.1m377 gold badges3.7k silver badges3.6k bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

KJW Over a year ago

which is the empty jar ? As far as I know all of them are at least 2KB in size.

BeauJest · Accepted Answer · 2013-09-18 03:18:45Z

1

We saw this issue as well for users with version 1.6.0_18.

I took a look at the jars listed in my jnlp file and found a license jar jumped out as a likely candidate for a jar with no classes. I confirmed this with jar tf.

As a quick test I removed the jar from the jnlp file and I did not get the error. However, I needed the license jar for a 3rd party library.

I updated my build file to bundle the license jar into my application jar

<jar jarfile="${dist}/lib/${application}.jar">
    <zipgroupfileset dir="${extLib}" includes="runtime.jar" />
...
</jar>

The 3rd party library could locate the license info in the classpath and no more errors!

answered Sep 18, 2013 at 3:18

BeauJest

513 bronze badges

1 Comment

Noumenon Over a year ago

I tried this and found some of my jars weren't in the folder at all, so try an ls *.jar too.

Collectives™ on Stack Overflow

Java Launch fails on second run: java.lang.NullPointerException

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related