Aaron Hagopian wrote:
It's JNDI itself. JNDI uses ABANDON requests. Are you using
persistent
search at all? Another 389 user reported similar problems caused by
improper handling of JNDI persistent searches + ABANDON requests.
Although this looks different, both issues have JNDI and ABANDON
in common.
We are not using persistent search at all. I will try to track down
what in our code creates the ABANDON requests but might take me a bit.
I think
it's JNDI itself - you probably won't find anything explicitly
calling an ABANDON request in your code.
Once successfull I'll get you something that causes the ABANDON
to
show up followed by a startTLS.
------------------------------------------------------------------------
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users