Gary Keim created DIRSERVER-2297:
------------------------------------
Summary: Connection exceptions now incorrect/have no causes
Key: DIRSERVER-2297
URL: https://issues.apache.org/jira/browse/DIRSERVER-2297
Project: Directory ApacheDS
Issue Type: Bug
Components: core-integ, ldap
Affects Versions: 2.0.0.AM25
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)
Reporter: Gary Keim
Attachments: apacheds-connect-defect.tar.gz
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
