Bridge for Git: Initialize repository failed with ENDEVOR_CONNECTION_ERROR

Products

• Endevor

Issue/Introduction

Bridge for Git Mapping initialization failed: 

Request ENDEVOR_RETRIEVE: 16:25:18  API0000S  SEVERE ERROR(S) DETECTED, PROCESSING TERMINATED
2026-03-23 21:25:31.128  INFO 33 --- [pool-2-thread-3] c.c.e.i.c.e.r.i.task.EndevorActionTask   : Running action ENDEVOR_RETRIEVE - request RetrieveElementRequest for 'ENV/STG/SYS/SUBSYS/TYPE/ELE'
2026-03-23 21:25:31.167  INFO 33 --- [pool-2-thread-3] o.apache.http.impl.execchain.RetryExec   : I/O exception (java.net.SocketException) caught when processing request to {}->http://host:port: Connection reset

 

2026-03-23 21:25:33.896  INFO 33 --- [pool-1-thread-11] c.c.e.i.m.b.j.i.s.WorkflowService        : 
| Operation: Initialize repository
| Mapping: XXXX
| Result: FAILED_RESTART - ENDEVOR_CONNECTION_ERROR
| User: XXX
| Summary: Endevor Connection is not available
| Messages:
|  - CONNECTION_REFUSED: Connection refused
|  - WARNING: The post-receive webhook was not triggered during initialization. Please check the webhook setup on the Git provider.
| Exception:
| com.ca.endevor.integration.connector.endevor.rest.exception.EndevorConnectionStatusException: CONNECTION_REFUSED: Connection refused

Environment

All supported Endevor Releases

Endevor Bridge for Git (B4G)

Cause

The Bridge for Git server cannot establish a socket connection to the Endevor Web Services due to network blocks, incorrect configuration, or the Web Services being inactive.

Resolution

1. Verify Web Services Status: Confirm the Endevor Web Services started task (WSTOMSTC) is running on the mainframe and listening on the expected port.
2. Test Connectivity: From the Bridge for Git server, run telnet <host> <port> to verify that the mainframe host is reachable and the port is open.
3. Validate Connection Settings: In the B4G application, go to Endevor Connections and verify:
   • The Host and Port match the mainframe Web Services configuration.
   • The Protocol (HTTP or HTTPS) matches the Web Services setup.
4. Check Firewall Rules: Ensure that any firewalls or security groups between the B4G server and the mainframe allow bidirectional traffic on the Web Services port.
5. SSL/Certificate Check: If using HTTPS, ensure the Endevor Web Services certificate is imported into the B4G server's Java trust store to prevent SSL handshake failures B4G Certification Path.
6. Webhook Configuration: Ensure the Git provider (e.g., GitLab) can reach the B4G server. The webhook URL should be: http://<B4G-IP>:<Port>/rest/evcs/v1/hooks/posthook

Additional Information

Multipe S80A abend found in the corresponding Endevor Web Services STC log:

+CCSR010E C1SSESTA S80A at 0003775C LMOD BSTPMOPS CSECT BSTP

The S80A error indicates a region size limitation. Currently, the Endevor STC JCL is set to REGION=7M. For B4G mapping with large Endevor inventories, this memory exhaustion can lead to web services connection resets.

To resolve this, implement the following changes:

1. Update the Endevor Web Service JCL to set REGION=0M to remove memory limits for the Endevor STC.
2. Recycle the Endevor web services Tomcat (WSTOMSTC).
3. Reinitialize the B4G mapping.