Max_waiters property left in an instance that has been upgraded causes the same Chat issues - Support and Troubleshooting

Max_waiters property left in an instance that has been upgraded causes the same Chat issues Issue

Symptoms This issue can produce blank pages or pages that seem to be loading but never do. It can also cause many different kinds of issues for things that rely heavily on requests such as Connect and Service Portal.

Look for the following in the application logs:

"WARNING *** WARNING *** GlideRequestManager:Request ignored: "

Release Kingston Jakarta Patch 6 and beyond Istanbul Patch 11 and beyond Cause A temporary workaround (adding and setting the com.glide.request.max_waiters system property) for a Chat related issue was left in an instance in which a permanent fix for the issue was applied. It essentially causes the same issue for the fixed instance for which it was applied as a temporary workaround earlier.

Resolution Remove the property. Go to the property.

Delete the value so there is no value.

Save the record.

This makes sure that the value of 20 does not get cached when you delete the property.

Delete the property completely from your instance.

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 HI to restart the instance which will clear the cached value. Please follow steps outlined in SOP - https://support.servicenow.com/kb_view.do?sysparm_article=KB0529173