This content has been marked as final. Show 6 replies
can you post the source code jnlp what you tried?? without seeing source code trying to answer is difficult.
I think it is because the java vm is not ready but I want to be sure this exception is related to the jvm.The exception was thrown by the JVM.
I have no access to the Configuration Panel to check if the jvm is installed.If the JVM wasn't installed it wouldn't be there to throw the exception, would it?
Note that you're not the first person to run into this error. I suggest you do a google for "Error while initializing manager: java.lang.NullPointerException, bail out" and see what you get.
Here's the launch.jnlp file...
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <jnlp href="launch.jnlp" spec="1.0+"> <information> <title>CSSMBulletins</title> <vendor>root</vendor> <homepage href=""/> <description>CSSMBulletins</description> <description kind="short">CSSMBulletins</description> <offline-allowed/> </information> <update check="background"/> <resources> <j2se version="1.6+"/> <jar href="CSSMBulletins.jar" main="true"/> <jar href="lib/mysql-connector-java-5.1.13-bin.jar"/> <jar href="lib/itextpdf-5.3.2.jar"/> </resources> <applet-desc height="750" main-class="cssmbulletins.CSSMBulletins" name="CSSMBulletins" width="1230"> </applet-desc> </jnlp>
Yes there is a lot of results I did that first ^^
I'm developping the Applet under Linux (opensuse 11.3) with NetBeans 7.0.1.
The clients are mostly Windows related but in my lab the only one client is Linux 11.4... never had issue concerning the one I'm trying to fix.
Some clients (Windows Seven or Windows XP) can not launch the Applet, they are connected to the Web server but I got this message.
I asked the administrator to check if java is up to date on all those computers that cause problem. I will have more informations tomorrow.
Thanx for your help, in advance ^^
The issue was fixed by simply update each jre on the client computers.
The problem was related to the fact that I had to ask to have admin rights to do it on each computers, fortunately it wasn't a lot of them that caused the issue.