MID Server OCSP timeouts not throwing exceptions causing connection to instance to stay foreverDescriptionThe MID Server agent log can show these kind of warnings, and connections can get stuck: Error: 07/29/20 11:04:27 (778) glide.lock.cleaner WARNING *** WARNING *** Freed stuck JVM lock: OCSPCheckedCertificateCache07/29/20 11:04:32 (737) Worker-Standard:JavascriptProbe-9cd773b24fe8a600f0c92ae6f110c720 [0:03:20.899] GlideSSLProtocolSocketFactory.walkCertChainToCheckIfRevoked of: CN=*.service-now.com, O="ServiceNow, Inc.", L=San Diego, ST=California, C=USSteps to Reproduce TBDWorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available. The intention is to add the following instructions to a KB article linked from the Documentation. 1. navigate to glide.properties under /agent/properties/glide.properties and add this property and value to the filecom.glide.communications.httpclient.ocsp_allow_network_error=false 2. Restart mid server Result: you would now see an exception and stack trace in the mid server logs on OCSP timeoutsRelated Problem: PRB1419209