Hello Guest

Fatal error occured (7)

  • 9 Replies
  • 9090 Views
Fatal error occured (7)
« on: December 26, 2007, 14:50:35 »
Hello, this error shout to me AppletLaoder "Fatal error occured (7)" can anybody clarify what does it mean??(no more hints i had recieved from java vm)
best regards and marry christmas!

*

Offline Matzon

  • *****
  • 2242
Re: Fatal error occured (7)
« Reply #1 on: December 26, 2007, 16:50:00 »
it means that it failed the STATE_SWITCHING_APPLET part.
Dont you get any more info?

it should output some more info:
"Fatal error occured (" + state + "): " + error;

Re: Fatal error occured (7)
« Reply #2 on: December 26, 2007, 21:44:16 »
no more info:(( really

*

Offline Matzon

  • *****
  • 2242
Re: Fatal error occured (7)
« Reply #3 on: December 27, 2007, 07:15:34 »
what os, drivers, gfx card, browser etc?
does regular lwjgl work ?

Re: Fatal error occured (7)
« Reply #4 on: December 27, 2007, 08:13:01 »
what os, drivers, gfx card, browser etc?
does regular lwjgl work ?

winxp sp2
OpenGL Version: 1.5.3
GeForce Go 6600/PCI/SSE2
firefox 2.0.0.11

regular lwjgl works with no problems for two years;)

the demo applet works also fine

my applet runs in netbeans with no problems, but not run directly in browser.

*

Offline Matzon

  • *****
  • 2242
Re: Fatal error occured (7)
« Reply #5 on: December 27, 2007, 14:40:41 »
aha. might be a signing issue then? please make sure that the relevant jars are signed

Re: Fatal error occured (7)
« Reply #6 on: January 01, 2008, 21:04:41 »
All YOURS applet are signed properly, none of MY applets is signed(but it loads data only from "server"). I have seen this error one more time when i "missversioned"  the jar in your demo(but in my applet this is alright)
Can it bee Not enough java heap space? I have set -xmX300m for applets in my jvm settings, but when i set more all applets stopped working. The application is really memory eater (10mb texture,2mb model and about 2mb of logic)
I have tested only on localhost.

Re: Fatal error occured (7)
« Reply #7 on: July 28, 2008, 14:58:31 »
hi,

i'm having the same problem. The example applet works, but my applet doesn't.

I get the following error message:
"An error occured while loading the applet. Please contact support to resolve this issue. Fatal error occured (7): src.Test"

might it really be a signing issue? My jar consists only of a single empty applet class.
Code: [Select]
package src;

import java.applet.Applet;
import java.awt.Graphics;


public class Test extends Applet {
@Override
public void paint(Graphics g) {
g.drawString("Hello", 40, 30);
}
}

do i really have to sign it? and if so, could someone help me with jarsigner??


thanks for help and sorry for my bad english.


here the console output:
Quote
Java Plug-in 1.6.0_03
Using JRE version 1.6.0_03 Java HotSpot(TM) Client VM

...
...
...

basic: Referencing classloader: sun.plugin.ClassLoaderInfo@765291, refcount=1
basic: Added progress listener: sun.plugin.util.GrayBoxPainter@1f12c4e
basic: Loading applet ...
basic: Initializing applet ...
basic: Starting applet ...
basic: completed perf rollup
security: Accessing keys and certificate in Mozilla user profile: C:\Documents and Settings\...\Application Data\Mozilla\Firefox\Profiles/........default
security: JSS package is not found
security: Loading Root CA certificates from C:\PROGRA~1\Java\JRE16~1.0_0\lib\security\cacerts
security: Loaded Root CA certificates from C:\PROGRA~1\Java\JRE16~1.0_0\lib\security\cacerts
security: Loading Deployment certificates from C:\Documents and Settings\hehe\Application Data\Sun\Java\Deployment\security\trusted.certs
security: Loaded Deployment certificates from C:\Documents and Settings\hehe\Application Data\Sun\Java\Deployment\security\trusted.certs
security: Loading certificates from Deployment session certificate store
security: Loaded certificates from Deployment session certificate store
security: Validate the certificate chain using CertPath API
security: Obtain certificate collection in Root CA certificate store
security: Obtain certificate collection in Root CA certificate store
security: The CRL support is disabled
security: The OCSP support is disabled
security: No timestamping info available
security: Checking if certificate is in Deployment denied certificate store
security: Checking if certificate is in Deployment permanent certificate store
Fatal error occured (7): src.Test

Re: Fatal error occured (7)
« Reply #8 on: July 29, 2008, 09:48:07 »

do i really have to sign it? and if so, could someone help me with jarsigner??


As far as I know, signing applets is about the same as signing jars for Web Start: you do not have to sign your jars if you do not access critical resources outside the sandbox (DLLs, read/write files, etc.). However if you want to use the LWJGL, you need its DLLs. So ultimately you will have to sign your jars.

It is not the easiest thing to do the first time, but there are many tutorials on the web. As a matter of fact I wrote one on how to sign jars for Web Start ;). Since a signed jar is a signed jar, it can also be applied to signing for applets. Just ignore the first paragraph about Web Start. It explains how to get a free certificate from Thawte (which is more trustworthy then a self-generated one) and how to use this certificate to sign your jars:
http://ciardhubh.de/node/4

Re: Fatal error occured (7)
« Reply #9 on: July 29, 2008, 13:23:19 »
i'll have a look at it. thanks!