TESTED_JAVA_RELEASE: Tiger

java version "1.5.0-internal"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-internal-jdeploy_04_may_2003_19_31)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b05, mixed mode)

TESTED_BUILD_LOCATION:
/net/sqesvr-nfs.sfbay/global/nfs/deployment3/tiger/PIT_builds/JD-PIT-01

TESTED_OS: SunOS 5.9

Description:
============
When I'm adding the SingleInstanceListener first time, an unique file with a name as given url is created under the .java/deployment/tmp/si/. Once the listener is removed and added again the same unique file is not created in the above stated location.

Other things are working fine, like if I launches the same application thru two diff JNLP files and with different contents then the application is treated like a normal application.

Herewith I'm attaching the sample application as application.jar and source code(SingleInstanceTest.java). Unjar the application.jar in a webserver and launch the application from the
homepage.html.

The application can be accessed from this location also:

http://cheran.india.sun.com:8080/jawstests/si/homepage.html

How to reproduce this bug?
==========================
Launch this application, you can find a frame with three buttons at the bottom, "Add", "Close" and "Remove". Click on the "Add" button will add the SingleInstanceListener and then launch the
application again. This works as expected, newActivation() method got invoked.

Now click on the "Remove" button and launch the application, a new instance of application get launched. Close the newly lauched application and click on the "Add" button, now launch theapplication again. You can notice an message saying that the SingleInstanceListener is added and still an new instance of application will be launched.

I'm using the tiger PIT build located in this following location:
/net/sqesvr-nfs.sfbay/global/nfs/deployment3/tiger/PIT_builds/JD-PIT-01