HPCC-35552 Improve logging when async connect fails

[ghalliday]

Type of change:

• This change is a bug fix (non-breaking change which fixes an issue).
• This change is a new feature (non-breaking change which adds functionality).
• This change improves the code (refactor or other change that does not change the functionality)
• This change fixes warnings (the fix does not alter the functionality or the generated code)
• This change is a breaking change (fix or feature that will cause existing behavior to change).
• This change alters the query API (existing queries will have to be recompiled)

Checklist:

• My code follows the code style of this project.
  • My code does not create any new warnings from compiler, build system, or lint.
• The commit message is properly formatted and free of typos.
  • The commit message title makes sense in a changelog, by itself.
  • The commit is signed.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly, or...
  • I have created a JIRA ticket to update the documentation.
  • Any new interfaces or exported functions are appropriately commented.
• I have read the CONTRIBUTORS document.
• The change has been fully tested:
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have checked that this change does not introduce memory leaks.
  • I have used Valgrind or similar tools to check for potential issues.
• I have given due consideration to all of the following potential concerns:
  • Scalability
  • Performance
  • Security
  • Thread-safety
  • Cloud-compatibility
  • Premature optimization
  • Existing deployed queries will not be broken
  • This change fixes the problem, not just the symptom
  • The target branch of this pull request is appropriate for such a change.
• There are no similar instances of the same problem that should be addressed
  • I have addressed them here
  • I have raised JIRA issues to address them separately
• This is a user interface / front-end modification
  • I have tested my changes in multiple modern browsers
  • The component(s) render as expected

Smoketest:

• Send notifications about my Pull Request position in Smoketest queue.
• Test my draft Pull Request.

Testing:

[ghalliday]

E.g.
000000E9 OPR 2026-01-02 16:48:27.729 3869613 3869674 "Failed to connect to 192.168.86.202:9001: EAFNOSUPPORT - Address family not supported by protocol family "

[github-actions]

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-35552

Jirabot Action Result:
Assigning user: gavin.halliday@lexisnexisrisk.com
Workflow Transition To: Merge Pending
Updated PR

[Copilot]

Pull request overview

This PR improves error logging when asynchronous socket connections fail by adding a new utility function and enhanced error messages that include the target endpoint and the specific error cause.

Key Changes:

• Added getSocketErrorMessage() function to expose socket error message formatting
• Enhanced connection failure logging with endpoint and error details in async connect callback

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
system/jlib/jsocket.hpp	Declares new getSocketErrorMessage() function to expose error message formatting
system/jlib/jsocket.cpp	Implements getSocketErrorMessage() wrapper around existing SocketException error formatting
system/security/securesocket/socketutils.cpp	Adds detailed error logging when async connect/reconnect fails, including endpoint and error cause

[dcamper]

Nice addition.

[ghalliday]

I had delayed merging this until I had thought about the connection failure case. Opened a new jira to discuss/address.

[github-actions]

Jirabot Action Result:
Added fix version: 10.2.0
Workflow Transition: 'Resolve issue'