-
Enhancement
-
Resolution: Fixed
-
P4
-
beta2, 5.0
-
b39
-
generic, sparc
-
generic, solaris
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2174420 | 5.0u19 | Kevin Walls | P3 | Resolved | Fixed | b01 |
| JDK-2161143 | 5.0u17-rev | Kevin Walls | P3 | Resolved | Fixed | b11 |
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
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
- backported by
-
JDK-2161143 Require a way to specify read timeout for LDAP operations
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-6446585 Client is hanging when using non LDAP port
-
- Closed
-
- relates to
-
-
- Resolved
-