url_response 4.46 and later: URL is delayed because of reason no thread is available

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

With url_resposne 4.46 and later (5.01, 5.02, 5.04) the following messages / alarms are seen for monitored profiles: 

URL is delayed because of reason no thread is available.
URL is delayed because of reason it is already running. 

Environment

• DX UIM 23.4.*
• url_response 4.6 and later

Cause

The explicit TLS 1.2 fallback mechanism implemented in url_response version 4.6 and subsequent releases can trigger thread contention and management overhead, resulting in the specific alarms described in this article.

Resolution

The build attached to this Article resolves the issue by deprecating the manual TLS 1.2 fallback logic and delegating protocol negotiation to the underlying security library, which natively manages secure handshaking and internal session handling.

To resolve the issue: 

1. Download the attached url_response (url_response-5.04-T1-20260320.171819-1.zip)

2. Import to IM 

3. Deploy to the affected url_response and verify if the alarms are still generated. 

Additional Information

NOTES: 

• This patch can be safely used in a production environment
• The subsequent GA version of url_response will include this code change.