1.6.0_23 JNLP2ClassLoader.findClass try again . slow jnlp applet loading

Question

Hello everyone,
I am using jnlp to load applet. using jre1.6.0_23. (next generation plugin).
While loading the applet I am getting following messages,
security: The root CA hasnt been replaced
security: No timestamping info available
security: Found jurisdiction list file
security: No need to checking trusted extension for this certificate
security: The CRL support is disabled
security: The OCSP support is disabled
security: This OCSP End Entity validation is disabled
security: Checking if certificate is in Deployment denied certificate store
security: Checking if certificate is in Deployment permanent certificate store
network: Cache entry not found [url: http://package/mic/ri/lib/japllet.jar, version: null]
basic: Plugin2ClassLoader.getPermissions CeilingPolicy allPerms
security: JAVAWS AppPolicy Permission requested for: http://testurl/test/ri/lib/jpllet.jar
basic: JNLP2ClassLoader.getPermissions() X
basic: JNLP2ClassLoader.findClass: com.pack.MyApplet: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.DefaultMICLookAndFeel: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.XMLScreen: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.JRenderer$1: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.TimeoutPopup: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.TransparentContainer: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.SwingWorker: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.JRenderer$10: try again ..
basic: JNLP2ClassLoader.findClass: com.pack.StatusPanel: try again ..
Let me know if anyone want to look at entire messages in java console.
for all the classes in jar which is signed.
JNLP I am using.
*<?xml version="1.0" encoding="UTF-8" ?>*
*<jnlp spec="1.0+">*
*<information>*
*<title>TestApp</title>*
*<vendor>TestApp</vendor>*
*</information>*
*<security>*
*<all-permissions/>*
*<j2ee-application-client-permissions/>*
*</security>*
*<resources>*
*<j2se version="1.6+"/>*
*<jar href="japllet.jar" main="true" version="0007.0000.0012.0000"/>*
*<property name="jnlp.versionEnabled" value="true"/>*
*</resources>*
*<applet-desc*
name="TestApplet"
main-class="com.pack.MyApplet"
width="300"
height="300">
*</applet-desc>*
*</jnlp>*
and am using the deployJava.js in html.. find below the snippet from html,
*+<script src=\"http://www.java.com/js/deployJava.js\"></script>+*
*+<script type="text/javascript">+*
+var attributes = {width:'100%', height:'100%'};+*
+var parameters = {jnlp_href:'mttest.jnlp'}+*
deployJava.runApplet(attributes, parameters, version);*
*+</script>+*
In the above script I have tried various combinations like codebase, code, type, archive. finally i kept the minimal attributes and parameters.
Kindly note my applet is working fine in the browser. But I think because of the try again messages in java console it is taking time to load the applet ?
Any help on this highly appreciated. I have almost spent my week trying to remove these messages.

Answer 1

837182 wrote:
..the last message of fetching resources japllet.jar is there as i changed the location. .. How? To what? I now note the applet Jar uses a version number, which JaNeLA fails to take into account.
..but how about rest of the messages, How to get rid of those ? ..Although I wrote the software, in conjunction with others, we did not configure it to send us an email when someone runs the software. Because of that (and hopefully unsurprisingly) I will state that I do not know what JaNeLA reported. OTOH I will make a WAG that there was an 'invalid content' message somewhere in the report.
Have you checked the JaNeLA Help page? It is the first place to check the error messages.
Some notes:
<li> Most of the errors are produced by J2SE inbuilt tools, and are messages common to XML validation. Search the net for them and you should find many hits.
<li> You can 'ignore' the warnings and optimizations. They are intended to identify things that might or might not be relevant. JaNeLA is unable to tell, and prompts you to make an informed decision.
As to whether it matters, consider this. I dealt with a failed JNLP launch that came down to illegal characters in the application title field. That is not something that JaNeLA even checks. But the simple principle is: Garbage In, Garbage Out. Before even considering why a JWS based launch is failing (or not working as you expect), it pays to ensure the input files are as logical and valid as we can make them. Otherwise 'all bets are off' as to how JWS clients will parse and act (or not) on the JNLP.
Reviewing the original problem now that you have at least run the JaNeLA tool. Just as an 'out there' suggestion, try adding a codebase_lookup='false' parameter into the applet code (JNLP launch file(1)). That attribute is only relevant to applets that can use loose class files & JWS should not need that, but it might indicate a JRE bug if it speeds things up.
1) ..Oh heck, throw it into the deployJava.js script as well. It will probably not help, but cannot hurt.
BTW: How big is apllet.jar in bytes? How 'slow' in seconds/minutes is slow? What is the network bandwidth of the testing machine(s)?
And now I remember to mention:
1) 'apllet' -> 'applet'.
2) Please use the code tags when posting Java or JavaScript code or snippets, XML/HTML/JNLP or input/output. For details see the 'sticky post' on the top of the forum thread listing. It is still possible to edit your original post to add the code tags.