Request ENDEVOR_GENERATE: Return code: 0012
Request ENDEVOR_GENERATE: Reason code: 0000
Request ENDEVOR_GENERATE: C1MSGS1: /reports/1732295301-3652176739704331-C1MSGS1
Request ENDEVOR_GENERATE: APIMSGS: /reports/1732295301-3652176739704331-APIMSGS
Request ENDEVOR_GENERATE: EWS1117I Request processed by SysID xxxx, STC WSEWSSTC - STCJOBNAME
Request ENDEVOR_GENERATE: 14:08:20 API0079E ERRORS WERE DETECTED. REVIEW THE C1MSGS1 EXECUTION REPORT FOR DETAILS
Request ENDEVOR_GENERATE: 14:08:20 API0000E ERROR(S) DETECTED, PROCESSING TERMINATED
Request ENDEVOR_GENERATE: 14:08:17 C1G0017E THE SELECTED ELEMENT IS CURRENTLY IN USE BY ANOTHER JOB OR USER. PLEASE TRY AGAIN
2024-11-22 17:08:56.286 INFO 2774315 --- [pool-5-thread-2] c.c.e.i.c.e.r.r.RetryableEndevorRequest : Retryable request failed and will be rerun in 490 ms (8 retries left)
2024-11-22 17:08:57.027 INFO 2774315 --- [pool-5-thread-8] c.c.e.i.c.e.r.r.RetryableEndevorRequest : Retryable request failed and will be rerun in 855 ms (8 retries left)
2024-11-22 17:08:57.456 INFO 2774315 --- [pool-5-thread-10] c.c.e.i.c.e.r.r.RetryableEndevorRequest : Retryable request failed and will be rerun in 1082 ms (8 retries left)
2024-11-22 17:09:11.877 INFO 2774315 --- [http-nio-8080-exec-7] c.c.e.boot.controller.HooksController : MF Webhook Event: 'EndevorActionPayload(actiontype=ELM, action=GENERATE, actiondate=20241122, actiontime=14090636, actionuserid=USRID, actionccid=XXXX, actioncomment=1CB642D COMMENT=9ELEMENTOS, actionpackageid=, processorgroup=PROCGRP, lastprocessor=PROCNAME, versionlevel=0108, lastleveldate=20241122, lastleveltim=null, sitename=* SiteName *, elementname=ELMNAME, toenvironment=XXXX, tosystem=XXXX, tosubsystem=XXXX, totype=COBOL, tostageID=S, actionreturncode=0000, fingerprint=0134DAE200CF6CDF)'
2024-11-22 17:09:11.888 INFO 2774315 --- [http-nio-8080-exec-7] c.c.e.b.c.helpers.MFWebhookHelper : MF Webhook Event: GENERATE 'xxxx/x/xxxx/xxxxx/xxxx/COBOL/ELMNAME (0134DAE200CF6CDF)'
2024-11-22 17:09:11.894 INFO 2774315 --- [http-nio-8080-exec-7] c.c.e.b.c.helpers.MFWebhookHelper : MF Webhook Event processed for 'xxxx/xxx/xxxxx/xxxx (develop)'
2024-11-22 17:09:11.927 INFO 2774315 --- [http-nio-8080-exec-7] c.c.e.b.c.helpers.MFWebhookHelper : LISTING: 'xxxx/xxxx/xxxxx//ELMNAME.CBL (xxxxxxx)'
2024-11-22 17:09:11.944 INFO 2774315 --- [http-nio-8080-exec-7] m.b.j.i.r.w.s.OperationSchedulingService : Refresh was already scheduled for branch 'xxxxx/xxxxx/xxxxx/xxxxx (develop)'
2024-11-22 17:09:27.188 ERROR 2774315 --- [pool-1-thread-4] c.c.e.i.m.s.s.api.model.db.Action : Executed action: ENDEVOR_GENERATE 'xxxx/x/xxxx/xxxxx//ELMNAME.CBL (0134DAE200CF6E08)' Result: ERROR_NORETRY
MFWebhook
BR4G
Endevor : All supported release
Those failures are always appearing quite close to the actual element in use error (C1G0017E). Retry happens when Bridge cannot connect to Endevor, or when there is STC shortage (EWS1111E)
The Bridge for Git application contains a retry logic. The retry logic enables the application to retry the request when there is an STC resource shortage, or when there is a request timeout.
In the application.yaml file; under the Endevor Configuration section:
Change the value of read-timeout-msec to extend the timeout to accommodate for longer generate times. This will force BR4G to wait for endevor web services response before retry logic kicks in.
# Endevor configuration
endevor:
# (Optional) REST API read timeout (in milliseconds)
# ! Minimum value: 1
# read-timeout-msec: 160000