Tested Build: j2re-1_5_0-fcs-bin-b99-windows-i586-01_sep_2003.exe

Build Location:
/net/altair.east/terra/space11/deployment/tiger-archives

The Singleinstance service is broken. This bug can be reproduced by launching any Singleton application.

While adding the SingleInstance listener it's creating the server port and singleinstance unique file, but for the next launch the application is treated as a normal application.

The same feature is working fine for Java Control Panel. For every launch of Java Control Panel, the single instance file gets created and removed once we closed the Control Panel

To reproduce this, launch the application in the following location
http://cheran.india.sun.com:8080/jawstests/si/si.jnlp

1. Launch the application
2. A frame with the 3 buttons get displayed
3. Click on the Add button to add the SingleInstance Listener
4. Launch the same application again

When you are launching the applciation the SI file got created in the ${Deployment home}/tmp/si. Launch the same application again.

A ClassCastException thrown in Java Console, which kind of blocks the subsequent launches of the Singleton application. This can be reproduced by killing the javaw.exe process using the task manager.

java.lang.ClassCastException: SingleInstanceTest
at com.sun.deploy.si.SingleInstanceImpl$2.run(SingleInstanceImpl.java:233)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.si.SingleInstanceImpl$SingleInstanceServer.run(SingleInstanceImpl.java:166)