Skip to main content

Build 7 applet initialization error

3 replies [Last post]
radvani7
Offline
Joined: 2005-10-10
Points: 0

Hi everyone,

I've noticed an occasional freeze occurs in build 7 -- this may have also been happening with build 6, but I can't be sure. Upon initializing the applet, Firefox 2.0 will freeze. This also happens with IE7. This occurs about 10% of the time. The console does not display any errors, as it freezes as well. The only way to get out is the kill the Firefox process. I checked the log files, and, thankfully, there is a stack trace. Here it is:

<?xml version="1.0" encoding="windows-1252" standalone="no"?>

Exception in thread "Thread-2" java.lang.ExceptionInInitializerError
at com.sun.deploy.util.DeployUIManager.setLookAndFeel(Unknown Source)
at sun.plugin.util.PluginSysUtil$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Caused by: java.util.ConcurrentModificationException
at java.util.IdentityHashMap$IdentityHashMapIterator.nextIndex(Unknown Source)
at java.util.IdentityHashMap$ValueIterator.next(Unknown Source)
at java.util.AbstractCollection.addAll(Unknown Source)
at java.util.HashSet.<init>(Unknown Source)
at sun.awt.AppContext.getAppContexts(Unknown Source)
at java.awt.Toolkit$DesktopPropertyChangeSupport.firePropertyChange(Unknown Source)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at java.awt.Toolkit.setDesktopProperty(Unknown Source)
at sun.awt.windows.WToolkit.updateProperties(Unknown Source)
at sun.awt.windows.WToolkit.lazilyInitWProps(Unknown Source)
at sun.awt.windows.WToolkit.lazilyLoadDesktopProperty(Unknown Source)
at java.awt.Toolkit.getDesktopProperty(Unknown Source)
at javax.swing.UIManager.<clinit>(Unknown Source)
... 3 more
Java Plug-in 1.6.0_10-ea

The source of the error seems to be a concurrent modification exception. I should mention that I'm using one 'trick' in this web-application which may be causing this. There are two pages in my web application: a splash page and the application page. The application page has the applet. However, because of longish cold-start times, I use the splash page to load a thin/fake applet, so that I can display a "Loading" message during the cold-start period. So when the user clicks 'Enter Site' on the splash page, I cold-start the fake applet and display Loading... Then when the fake applet is finished loading the user enters the application page, where the real applet is loaded, and where this error is thrown.

This may have nothing to do with the problem, but I thought I would throw it in there. Thanks!

Raj Advani
www.upnext.com

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
radvani7
Offline
Joined: 2005-10-10
Points: 0

I should mention, I'm using Windows XP.

qu0ll
Offline
Joined: 2006-12-09
Points: 0

This would appear to be the exact same problem I reported yesterday. Thanks for adding the stack trace.

--
And loving it,

-Q
_________________________________________________
Qu0llSixFour@gmail.com
(Replace the "SixFour" with numbers to email me)

qu0ll
Offline
Joined: 2006-12-09
Points: 0

radvani7:

You may find that there is another way to display a "Loading" message in your large applet. What I am doing is to have a small applet class and a larger "worker" class. I also have an interface that defines the relationship between the two. Then, I program the applet against the interface and only load the worker class by using Class.forName(). This means that the applet class loads very quickly and then the worker class is loaded. It's then a simple matter to override paint() in the applet to display "Loading" until the worker is active.

I hope this helps.

--
And loving it,

-Q
_________________________________________________
Qu0llSixFour@gmail.com
(Replace the "SixFour" with numbers to email me)