The failure (400) of Nexus API service causes task execution failed and generates intermittent occurrences of "Unexpected Error" issues with low frequency from plan/task execution.
Cause
Nexus Log
10.80.3.171 - admin [01/Apr/2024:05:03:31 +0800] "GET /service/rest/v1/search/assets/download?repository=releases&maven.groupId=xxx&xx&version=2.0.0&maven.extension=zip.md5&maven.classifier= HTTP/1.1" 400 - 184 6 "Apache-HttpClient/4.5.10 (Java/1.8.0_292-ea)" [qtp661824503-136003]
TAC Log
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - org.talend.exception.BusinessException: There is no artifact for task 'job_xxx_ingestion_v2' in NEXUS 3 Repository.
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - java.util.zip.ZipException: error in opening zip file
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - org.talend.json.JSONException: JSONObject["filePath"] not found.
These above logs from both TAC and Nexus reveal that the Nexus server's REST API failed to provide a correct status code (200), which is essential for the successful completion of the TAC zip downloading process. The Nexus API service response resulted in a 400 error and this failure (400) causes the execution of plans/tasks to fail.
The root cause of this failure (400) of Nexus API service issue could be attributed to
- A high-load scenario on the Nexus server is increasing the response times for downloading requests.
- Sporadic network interruptions affect Nexus connectivity stability.
Resolution
Boost the Nexus with longer session time by modifying the following UI settings
- Navigate to: Nexus -> System -> Capabilities -> Setting
- Increase the duration for the following settings to accommodate longer session times
Session Timeout
Standard Request Timeout
Extended Request Timeout
Enhance Monitoring
- Implement performance monitoring for Nexus request logs to identify and address any bottlenecks promptly.
- Monitor network quality to detect and mitigate any connectivity issues affecting Nexus operations.
Environment
Talend Administration Center
