jdk1.5 found unsigned entry in resource

Testing just now with webstart on windows with JDK version 1.5 I came across an error where webstart refused to launch my application claiming "found unsigned entry in resource". In other words, it claimed that my jar file was not properly signed. But the jar file IS properly signed, and worked fine with java 1.4.

A little research on forum.java.sun showed that others have had this problem and that the solution is simply to try again. After reloading the jnlp file three times, the problem went away.

I don't like the idea that my customers may have to do this. They would probably assume there was an error in our application, not an error in WebStart, and might not be willing to re-try three times.

Anyone else seen this problem?

Know any work-arounds? Maybe I need to use a jdk1.5 jarsigner rather than the jdk1.4 jarsigner?

Hello Ed!

I have this problem as well with 1.5.0. I get the error the first time I try to start the app when it needs to download the jars - when I click the link again, it tries again and downloads it without complaining about anything.

I have yet to find a solution to this. I think it may be a bug that's been there since 1.4.2:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4920115

.. but that one is closed, since it's a duplicate of this bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4924188

.. which is missing.

Here is another link at the sun site about this bug. It seems to have been around for a long time:

http://forum.java.sun.com/thread.jspa?threadID=212136&messageID=727737

I had this problem on 1.6. It happened consistently, even after several tries. Turns out the PC I was on had disabled Java caching.

To fix:

Open Java Control Panel (from the Windows Control Panel)
Under the General tab, click “Settings…” in Temporary Internet Files
Check the “Keep temporary files on my computer” checkbox

Somaiah is right. Disabling Java plugin caching is sometimes causing this error. I investigated this deeper and found the reason why it happens. Some antries in META-INF/MANIFEST.MF need to be removed to make the JAR working. Read my blogpost: http://blog.atlashost.eu/post/found-unsigned-entry-in-resource-java-web-start.html

It's sad that this bug remains for *years* there...

Hi Somaiah & Damian, I already have the "Keep temporary files on my computer" option checked and yet face the issue. Any other workaround? My application is slightly different though: it is a JavaFX 2.0 application signed using JavaFX's <fx:signjar> ant target. Any pointers would be highly appreciated!

Also, can we not run a JNLP app without signing it in the first place?

Thanks,
Ravi.

Hi shrihari, and welcome to the Ranch!

I'm not sure whether Somaiah and Damian still visit this forum, as they both posted only once some time ago.

Other people here might still be able to help you, though. You should probably tell us what your problem is (the exact error message etc.). In any case, you can use
to see whether the file is correctly signed.