JDK-4403952 : remove dependency on Thread.interrupt()
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 1.4.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 2001-01-11
  • Updated: 2001-02-05
  • Resolved: 2001-02-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.0 betaFixed
Related Reports
Relates :  
JDK-4211692 - thread.interrupt does not work as expected with some versions of the VM.
Relates :  
JDK-4779765 - LDAP provider hangs when doing DIGEST-MD5 authentication
Description
Thread.interrupt() works only on Solaris for socket IO. The LDAP provider depends on interruptible socket IO for supporting StartTLS and SASL authentication. The LDAP provider must be changed to avoid dependence
on Thread.interrupt().
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
02-09-2004
EVALUATION When an LDAP operation that potentially requires the socket read to be interrupted is performed, set a flag in the request so that when the response is returned, the reader thread waits on a lock instead of the read. Do this for extendedOperation in which the operation is StartTLS, and do this for SASL bind. When each LDAP operation is sent, unblock the reader thread if necessary so that it can read the reply. When the StartTLS connection is closed (nonfatally), set a flag to let the reader know that the input stream is about to be closed, and to wait to be unblocked so that the stream can be replaced. rosanna.lee@eng 2001-01-11
11-01-2001