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.
Resolve Chat issues caused by the max_waiters property after an upgrade - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolve Chat issues caused by the max_waiters property after an upgrade
KB0683895

Resolve Chat issues caused by the max_waiters property after an upgrade


1636 Views Last updated : Jun 19, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

The max_waiters property setting can cause issues with Service Portal and other features that rely heavily on requests, such as Chat and Connect. It can lead to:

  • Blank pages
  • Pages that seem to load but never complete
  • Various other issues with request-based features

Look for the following in the application logs:

"WARNING *** WARNING *** GlideRequestManager:Request ignored: <some_transaction>"

Release

  • Kingston
  • Jakarta Patch 6 and beyond
  • Istanbul Patch 11 and beyond

Cause

A temporary fix (adding and setting the system property com.glide.request.max_waiters) was applied to an instance to resolve a Chat-related issue. Later, a permanent fix for the same issue was applied to the instance. However, the temporary fix was not removed after the permanent fix was applied, which resulted in the same issue reappearing that the temporary fix was intended to resolve. 

Resolution

To solve this, remove the property. 
  1. Go to the property.
  2. Delete the value so there is no value.
  3. Save the record. This makes sure that the value of 20 does not get cached when you delete the property.
  4. Delete the property completely from your instance.
  5. In scripts background, run gs.print(gs.getProperty('com.glide.request.max_waiters')); to verify the cached value has been removed. You should expect to see a value of 'null'

If you get any other value, you will have to create a standard change in NowSupport to restart the instance, which will clear the cached value. To do this, follow steps outlined in the knowledge article, Standard Change: Node restarts using Datacenter


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.