-
Sub-task
-
Resolution: Delivered
-
P4
-
6u211, 7u191, 7u201, 8u181, 8u191, 11.0.1, 12
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8213495 | 12 | Clifford Wayne | P4 | Resolved | Delivered | |
| JDK-8211873 | 11.0.1 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8211872 | 8u191 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8212012 | 8u181 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8289247 | 7u201 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8211898 | 7u191 | Clifford Wayne | P4 | Closed | Delivered | |
| JDK-8211871 | 6u211 | Clifford Wayne | P4 | Closed | Delivered |
Application code using LDAPS with a socket connect timeout that is <= 0 ( the default value ), may encounter an exception when establishing the connection.
The top most frames from Exception stack traces of applications encountering such issues might resemble the following:
```
javax.naming.ServiceUnavailableException: <server:port>; socket closed
at com.sun.jndi.ldap.Connection.readReply(Unknown Source)
at com.sun.jndi.ldap.LdapClient.ldapBind(Unknown Source)
...
```
The top most frames from Exception stack traces of applications encountering such issues might resemble the following:
```
javax.naming.ServiceUnavailableException: <server:port>; socket closed
at com.sun.jndi.ldap.Connection.readReply(Unknown Source)
at com.sun.jndi.ldap.LdapClient.ldapBind(Unknown Source)
...
```
- backported by
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
(2 backported by)