This bug also probably exists in 4.0.0 and should be evaluated in order to determined whether it is a blocker for 4.0.0.
Steps to reproduce:
- install two opendj instances replicated using the admin guide Example.ldif
- setup proxy to load balance across both servers
- performing an anonymous LDAP search against the proxy fails with suspicious error code
- access logs on backend server indicate an NPE:
- and the error logs on the backend server provide more details:
- the error is propagated to the proxy and finally back to the client. The proxy access logs sometimes contain the NPE and sometimes don't: