Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 1.2.0
Affects Version/s: 1.1.6, 1.1.7, 1.2.0
Component/s: hotspot
Labels:
- licbug

Subcomponent:
runtime
Resolved In Build:
1.2fcs
CPU:

generic, sparc
OS:

generic, solaris_2.5.1, solaris_2.6
Verification:
Not verified

Calling close on a file descriptor that is being used by another thread
blocks on Solaris native threads, but succeeeds immediately on green
threads and Win32. Solaris native threads I/O needs to be fixed so that
it behaves the same as green threads and Win32. In addition, the API
documentation needs to be updated to state this as a feature programmers
can rely on.

This is a critically useful feature that applications like Hotjava can
rely on to terminate long-running IO operations. Interruptable IO would
also do the job, but we are finding it very difficult to support on
Win32.

duplicates

JDK-4144981 Simultaneous socketAccept/socketClose deadlocks under native threads

Closed

JDK-4147067 native threads: Thread( runnable ) where runnable opens server socket hangs

Closed

JDK-4208094 Socket.close() blocks with Solaris native UI threads

Closed

JDK-4210924 Solaris 2.5.1 - Socket.close() hangs on Socket.read() on different thread

Closed

JDK-4107121 closing a ServerSocket that's in accept() fails

Closed

Assignee:: Hong Zhang

Reporter:: Sheng Liang (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 1997-12-03 19:13

Updated:: 1999-01-14 22:42

Resolved:: 1999-01-14 22:42

Imported:: 17/Sep/12 10:12 PM

Indexed:: 28/Jul/12 5:30 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates