United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6382902 VM interrupted I/O feature put on an option switch (sol)
JDK-6382902 : VM interrupted I/O feature put on an option switch (sol)

Details
Type:
Enhancement
Submit Date:
2006-02-08
Status:
Closed
Updated Date:
2012-10-13
Project Name:
JDK
Resolved Date:
2006-03-31
Component:
hotspot
OS:
solaris,solaris_2.5.1
Sub-Component:
runtime
CPU:
sparc,generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.2,5.0u9,6
Fixed Versions:

Related Reports
Backport:
Backport:
Duplicate:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

Description
This RFE provides a Solaris-specific XX option switch for the Solaris JVM to enable initial Sun-internal testing. This RFE does not cause any behavior change on Solaris or elsewhere with the default setting of the new switch.
 
A major fraction (but not all) of the Java SE feature called "Interruptible I/O" is Solaris-specific and stemming from specific code in os::interrupt to do thr_kill calls in response to Java Thread.interrupt() and specific differences between the _INTERRUPTIBLE macro code in os_solaris.inline.hpp vs counterpart code for the Linux and Windows JVMs. 

In order to help identify any applications that have dependencies on the Solaris-specific behavior stemming from these JVM differences, if any still exist, a convenient means of disabling the specific behavior is needed. This RFE will provide the XX switch "UseVMInterruptibleIO" in Solaris JVMs, with a default swtting to "on"(true), for a net zero change of behavior for the ordinary use case. 

But with -XX:-UseVMInterruptibleIO, Java SE on Solaris users can test the behavior of their applications when the primary source of interruption is cut off. (Primary, because there are other, minor, sources of interruption that are platform-independent in the JDK and it is only the Solaris-specific behavior that is of interest). A less likely, but still possible dependency that can also be tested with this option is where an application runs properly on Linux or Windows but fails to run properly on Solaris because of the OS-specific I/O interruption capability.

                                    

Comments
EVALUATION

Making this option available in Mustang allows discovery and elimination of any dependencies, assuming any dependencies still exist.
                                     
2006-02-08
EVALUATION

This switch is being labeled "unstable", meaning it could be withdrawn from Hotspot at any time or be relabeled in the future. This switch has no formal status whatsoever until/unless JAT approves it's mention in the Mustang release notes.
                                     
2006-03-07
EVALUATION

If this switch is back ported to other Java SE versions the release notes must be updated too.
                                     
2006-10-27
EVALUATION

This switch was approved for inclusion in Java SE 6 and is documented in the Solaris-specific release notes for that version.
                                     
2006-10-31
EVALUATION

This switch has been back-ported to Java SE 5 update 12 with a default setting and behavior identical to that of the switch in SE 6.
                                     
2007-05-08



Hardware and Software, Engineered to Work Together