As you noticed, the Java Web Start error message is not very helpful in that it does not say which JAR or JARs are signed with different certs.
What release of Java SE are you using on the server and the client?
This is quite odd, because all the files listed in the __system.jnlp are provided by GlassFish. Further, GlassFish signs them automatically using the self-signed certificate that the domain generates when it is created.
So, either the signed files on the server are no longer correct or for some reason the Java Web Start cache on the client somehow contains some GlassFish system files signed with one cert and some signed with another.
Here is one thing you can try.
optional step 0: Clear out the Java Web Start cache. You can use javaws -viewer and then navigate to the cache viewer, choose Resources from the drop list, and find the line for the __system.jnlp file. Then delete that. It should also remove the cached JARs listed in that JNLP document.
1. Stop the GlassFish server.
2. Delete the directory ${domainDir}/java-web-start. (Probably, ${domainDir} is domains/domain1 under your GlassFish installation directory.
3. Restart the server.
4. Try to launch the app client from the client system again.
The launch will take some time, because we are forcing the server to sign the required GlassFish system files again and then the client will have to download the newer versions of the files to refresh its cache. (And yes, we know there are too many files there! Reducing the number and size is a goal; just not accomplished yet.)
What this will not tell us is how you got into this state.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=478423