JDK-6176036 : Require a way to specify read timeout for LDAP operations
- Type: Enhancement
- Component: core-libs
- Sub-Component: javax.naming
- Affected Version: beta2,5.0
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic,solaris
- CPU: generic,sparc
- Submitted: 2004-10-08
- Updated: 2017-05-16
- Resolved: 2005-06-02
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.
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 | Other | JDK 6 |
|---|---|---|
| 5.0u17-revFixed | 5.0u19Fixed | 6 b39Fixed  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
When a JNDI client is doing an LDAP operation, if there is no response from the server, the client blocks on the LDAP operation to get the response back from the server. Many customers and developers have encounterd this situation and they come back to us with the problem of a 'client hang'. The workarounds like interrupting the operation by running a parallel thread that acts as a timekeeper have been suggested. However, customers would like to have a way of specifying the read timeout through the JNDI APIs directly as the workarounds add extra overhead on the application developers and do not provide the required flexibility. ###@###.### 10/8/04 07:12 GMT
Comments
|