The LDAPConnection search method (Novell library) that this monitor uses does not provide a way to limit how long we will wait for the search to complete on the server. This is bad because it enables a badly-behaved LDAP server to cause the poller to leak threads.
Issue reported by support customer under ticket https://mynms.opennms.com/Ticket/Display.html?id=2513
We should be using the search method which takes an instance of LDAPSearchConstraints to set both a local timeout (probably equal to "timeout" parameter) to avoid the thread leak and a server-side time limit (whole seconds; round up our timeout to the next second?) for the sake of politeness.