Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
LDAP listener is terminated and not restarted when there is an unknown exception - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • LDAP listener is terminated and not restarted when there is an unknown exception
KB0758342

LDAP listener is terminated and not restarted when there is an unknown exception


2020 Views Last updated : Mar 18, 2025 public Copy Permalink
KB Summary by Now Assist

Description

When an LDAP listener catches any exception other than NamingException or InterruptedNamingException, the LDAP listener is silently terminated.

Steps to Reproduce

This issue may occur intermittently.

  1. Setup an LDAP server.
    2. Start the listener.

To start listener follow these steps:

  • Navigate to All > System LDAP > LDAP Servers.
  • Select the LDAP server to configure.
  • Select the Listener check box.
  • Click Update.
     

3. If an exception other than NamingException or InterruptedNamingException is caught, the LDAP listener is terminated.

The exception will be logged in the logs before the below warning of the listener being terminated. 

06/13/19 12:18:29 (761) glide.ldap.listener-48d67f4ddbfecb4051cb3a90ad96199a WARNING *** WARNING *** LDAP listening terminated

Workaround

After carefully considering the severity and frequency of this problem and the risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make these decisions lightly, and we apologize for any inconvenience.

Workaround

From the LDAP server record, stop and start the listener again. 


Related Problem: PRB1349958

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.