JDK-7007021 : applications not getting closed while killing IE using System.exit(0)
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u24
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2010-12-15
  • Updated: 2013-03-12
  • Resolved: 2013-03-12
Related Reports
Relates :  
JDK-6847511 - plugin2 crash in mshtml.dll / sun.plugin2.main.server.IExplorerPlugin.javaScriptReleaseObject
Description
J2SE Version (please include all output from java -version flag):

	java version "1.6.0_23"
	Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
	Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)

	java version "1.6.0_24-ea"
	Java(TM) SE Runtime Environment (build 1.6.0_24-ea-b01)
	Java HotSpot(TM) Client VM (build 19.1-b01, mixed mode, sharing)

	java version "1.6.0_24-ea"
	Java(TM) SE Runtime Environment (build 1.6.0_24-ea-b02)
	Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)


Does this problem occur on J2SE 5.0.x or 6ux ?  

	Jre 16U23,16U24



Operating System Configuration Information:

	WinXP with SP 3


Hardware Configuration Information:

	x86



Bug Description:

Customer application is not getting closed while killing IE using System.exit(0) 
with Jre 16U23 and 16U24, whereas the same code is working with Jre 16U22 
and lower versions.

show a Sign-on Message dialog with Yes and NO button and the user has to click 
Yes to access the application, and by clicking on the 'No' button, 
the application should get closed.


With Jre 16U23/24, while clicking 'NO' button, the application gets hang instead of closing. There is no client side and java console exceptions. Whereas, application is getting closed on clicking No button with Jre 16U22 and lower versions.

Root Cause:

per their investigation, the System.exit(0) is not working with Jre 16U23/24. 
The responsible code is present in 'myprofile/CustomMessageUtils.java' line 
no 155 and 228. Since there is no exception in the client logs, They have 
captured the log folder of 
'C:\\Documents and Settings\\<user Name>\\Application Data\\Sun\\Java\\Deployment\\log\' 

at the time of the issue with 6U23, 6U24-b01, and 6U24-b02 jre versions. 

Attached the log folder and screenshot fyr.
Comments
closing as not an issue as per Calvin's comments above.
12-03-2013
EVALUATION With JRE 6u23 b01, although the browser windows closed upon clickin on "No" in the "Platform Activation" dialog (see attached PlatformActivation.PNG). The browser actually crashed with access violation. The call stack is as follows: > mshtml.dll!3d0e9751() mshtml.dll!3cfa06e0() mshtml.dll!3cf9de69() mshtml.dll!3cf7a5d6() jp2iexp.dll!6d413179() The crash problem is the same as 6847511. Since the "Platform Activation" dialog is running within the client vm (java.exe) process, calling System.exit() should only terminate the client vm and shouldn't have any effect on the browser process. The behavior seen with 6u23 b02 is correct. Only the "Platform Activation" dialog got disposed upon clicking on "No". The browser process remains running. If the customer wants to close the browser window, they should use the javascript approach as described in 6847511. Removing the "regression" keyword since this isn't a regression and lowering its priority to 4.
21-12-2010
EVALUATION This bug is introduced by the fix of the following bug: 6921935: Java Runtime Error (EXCEPTION_ACCESS_VIOLATION) in [mshtml.dll+0x249889] Which is putback into JRE 6u23 b02. I have tested using JRE 6u24 and backout the above fix, the issue is going away.
16-12-2010