[DIRSERVER-2297] Connection exceptions now incorrect/have no causes

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0.AM25
• Component/s: core-integ, ldap

Environment

openjdk version "1.8.0_232"
OpenJDK Runtime Environment (Zulu 8.42.0.23-CA-macosx) (build 1.8.0_232-b18)
OpenJDK 64-Bit Server VM (Zulu 8.42.0.23-CA-macosx) (build 25.232-b18, mixed mode)

openjdk version "11.0.5" 2019-10-15 LTS
OpenJDK Runtime Environment Zulu11.35+15-CA (build 11.0.5+10-LTS)
OpenJDK 64-Bit Server VM Zulu11.35+15-CA (build 11.0.5+10-LTS, mixed mode)

• Assignee: Unassigned
• Reporter: Gary Keim
• Created: 03/Jan/20 18:16
• Updated: 03/Jan/20 18:16

Description

With the most recent Zulu JDK versions, an exception raised when trying to connect to an "ldaps" transport via an "ldap://" url is unrelated to the real problem and the actual cause is not chained in to the thrown NamingException. The actual cause is shown on stdout.

NamingException raised: LDAP response read timed out, timeout used:-1ms.

Expected: ServiceUnavailableException

The attached Maven project demonstrates the problem.