This content has been marked as final. Show 6 replies
The same code is working on many other clients without problems.
The same code is working on many other clients without problems.Yes you said this in your first post.
I don't have an ideas for workarounds given your requirement that the exception not show up in the console, but I would just comment that scanning the console for the traces of exceptions and taking actions based on that is not generally a good strategy. Java has all the facilities (ie try/catch) you need to handle these problems directly and you avoid problems like this
I agree that scanning java console and taking actions based on this is not a good idea :-)
But we aren't doing that. Normally I don't read the java console log, but I was searching for a reason for not working clients on customer side.
I hoped to get an information in which situation such an error could occur (maybe incomplete appet loading, timing problems).
Depending on the message text it could be a solution to ignore this very special exception. But this is not a very smart solution.
- Enable full tracing details. See here:
- Does your customer run plugin1 or plugin2?
- Can he see same issue with JRE7?
And with latest beta drop - http://jdk7.java.net/download.html ?
- Is it first call to the applet that fails?
Can you add test callbacks from applet to js code to see if live connect is working?
Do they work before fist attempt to call applet?
Thanks for the excellent link.
I will ask the customer to turn on full trace.
I think the customer is running plugin2. I asked him to make the oracle installation test. He reported that an older java version is found: Java SE Update 21 on Firefox and that the test throws a java exception with Internet Explorer: java.lang.ClassNotFoundException: testJava2_1.TestVMApplet.class.
I'm a little bit irritated about the 'SE' in the java version.
It is the first call to the applet that fails.
Maybe there are proxy problems on some browsers.