FULL PRODUCT VERSION :
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
It is impossible to shutdown a Webstart application without System.exit(). It is likely this hang is caused by Webstart spawning its own non-daemon threads which prevent a clean shutdown.
Using System.exit() is not an alternative for my product because we use native code and we absolutely *must* know whether a clean shutdown has occured.
Please fix this within the Tiger timeframe, not Mustang.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Clean shutdown when no threads remain
ACTUAL -
Hang on shutdown
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
Compile the application code into test.jar, sign it, modify the JNLP file to point to it and run the application by hitting the JNLP file from a browser.
---- The application ----
public class Test
{
public static void main(String[] args)
{
System.out.println("hello");
}
}
--------------------------------
---- The JNLP file ----
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="http://hostname.com/jnlp" href="test.jnlp">
<information>
<title>test</title>
<vendor>vendor</vendor>
<homepage href="http://www.hostname.com/" />
<description>Shutdown test</description>
</information>
<offline-allowed/>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+" java-vm-args="-esa -Xincgc -Xmx20m"/>
<jar href="test.jar"/>
</resources>
<application-desc main-class="Test"/>
</jnlp>
------------------------------------------------------
---------- END SOURCE ----------
###@###.### 2005-1-07 21:09:50 GMT
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
It is impossible to shutdown a Webstart application without System.exit(). It is likely this hang is caused by Webstart spawning its own non-daemon threads which prevent a clean shutdown.
Using System.exit() is not an alternative for my product because we use native code and we absolutely *must* know whether a clean shutdown has occured.
Please fix this within the Tiger timeframe, not Mustang.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Clean shutdown when no threads remain
ACTUAL -
Hang on shutdown
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
Compile the application code into test.jar, sign it, modify the JNLP file to point to it and run the application by hitting the JNLP file from a browser.
---- The application ----
public class Test
{
public static void main(String[] args)
{
System.out.println("hello");
}
}
--------------------------------
---- The JNLP file ----
<?xml version="1.0" encoding="UTF-8"?>
<jnlp spec="1.0+" codebase="http://hostname.com/jnlp" href="test.jnlp">
<information>
<title>test</title>
<vendor>vendor</vendor>
<homepage href="http://www.hostname.com/" />
<description>Shutdown test</description>
</information>
<offline-allowed/>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.5+" java-vm-args="-esa -Xincgc -Xmx20m"/>
<jar href="test.jar"/>
</resources>
<application-desc main-class="Test"/>
</jnlp>
------------------------------------------------------
---------- END SOURCE ----------
###@###.### 2005-1-07 21:09:50 GMT
- duplicates
-
JDK-6214784 REGRESSION:TraceMsgQueueChecker is written unsafely
-
- Resolved
-