Telemetry job failed due to a connection closed (timeout)
search cancel

Telemetry job failed due to a connection closed (timeout)

book

Article ID: 278076

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Telemetry job failed with the below error message: 
 
ERROR 2024-01-09 23:30:05,943 [Dispatch TELEMETRY_JOB : bg@XXXXXX (tenant=clarity)] analytics.AnalyticsClient (clarity:XXXXXXX:TELEMETRY_JOB) () Error Sending Data to Broadcom telemetry
org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected
at org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedInputStream.java:263)
at org.apache.http.impl.io.ChunkedInputStream.nextChunk(ChunkedInputStream.java:222)
at org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:147)
at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:118)
at java.base/java.util.zip.CheckedInputStream.read(CheckedInputStream.java:60)
[....]
ERROR 2024-01-09 23:30:05,944 [Dispatch TELEMETRY_JOB : bg@XXXXX (tenant=clarity)] analytics.AnalyticsClient (clarity:XXXXXXX:TELEMETRY_JOB) () Error Sending Data to Broadcom telemetry
INFO  2024-01-09 23:30:06,068 [Dispatch TELEMETRY_JOB : bg@XXXXXX (tenant=clarity)] njs.scheduler (clarity:XXXXXXX:TELEMETRY_JOB) () BGTask.run: Job ID: 5079024; start date: 2024-01-09 23:30:00.127 with Status: COMPLETED, finish date: 2024-01-09 23:30:05.972, job code: TELEMETRY_JOB, duration: 00:00:05.845

Resolution

This job runs daily, if the next runs are going through fine, then it may be just a one off timeout error which can safely be ignored