Support Questions
Find answers, ask questions, and share your expertise

Ambari Server logs : "AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl"

Ambari Server logs : "AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl"

Explorer

Hi,

Since we installed ambari server 2.5.2 (with ldap users) we see the server logging (starts randomly) without stopping :

 07 Nov 2017 08:09:59,653  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,670  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,686  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,703  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,723  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,740  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,756  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,772  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,791  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,807  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,824  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,842  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,858  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,875  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl
07 Nov 2017 08:09:59,891  INFO [pool-17-thread-15] AbstractRequestControlDirContextProcessor:198 - No matching response control found - looking for 'class javax.naming.ldap.PagedResultsResponseControl


After this we need to restart the server since it became unstable and not responsive.

Is this a known bug ? And if so, what can I do to fix this ?

Kind regards

Manfred