United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6176036 Require a way to specify read timeout for LDAP operations
JDK-6176036 : Require a way to specify read timeout for LDAP operations

Details
Type:
Enhancement
Submit Date:
2004-10-08
Status:
Resolved
Updated Date:
2010-05-10
Project Name:
JDK
Resolved Date:
2005-06-02
Component:
core-libs
OS:
solaris,generic
Sub-Component:
javax.naming
CPU:
sparc,generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
beta2,5.0
Fixed Versions:

Related Reports
Backport:
Backport:
Duplicate:
Relates:

Sub Tasks

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
EVALUATION

See comments.
###@###.### 10/11/04 07:47 GMT
                                     
2004-10-11



Hardware and Software, Engineered to Work Together