Describe the bug
When an error occures in the LDES Client, the pipeline gets HALTED. However, I would also expect to still be able to retrieve the ldes-client status, which would be ERROR in this case
Expected behavior
Being able to retrieve the ldes client status ERROR when an error occures in the LDES Client
Screenshot
Logs
2024-08-20 08:44:49 2024-08-20T06:44:49.007Z INFO 1 --- [nio-8080-exec-7] b.v.i.l.l.pipeline.PipelineServiceImpl : CREATION of pipeline 'validation-pipeline' successfully finished
2024-08-20 08:44:49 2024-08-20T06:44:49.007Z INFO 1 --- [pool-5-thread-1] l.c.s.StartingTreeNodeFinder : determineStartingTreeNode for: http://localhost:8082/verkeersmetingen
2024-08-20 08:44:49 2024-08-20T06:44:49.131Z WARN 1 --- [pool-5-thread-1] l.l.r.e.r.BasicIntervalFunctionDecorator : Retrying request (attempt #1) after null response
2024-08-20 08:44:49 2024-08-20T06:44:49.485Z WARN 1 --- [pool-5-thread-1] l.l.r.e.r.BasicIntervalFunctionDecorator : Retrying request (attempt #2) after null response
2024-08-20 08:44:50 2024-08-20T06:44:50.431Z WARN 1 --- [pool-5-thread-1] l.l.r.e.r.BasicIntervalFunctionDecorator : Retrying request (attempt #3) after null response
2024-08-20 08:44:51 2024-08-20T06:44:51.843Z WARN 1 --- [pool-5-thread-1] l.l.r.e.r.BasicIntervalFunctionDecorator : Retrying request (attempt #4) after null response
2024-08-20 08:44:52 2024-08-20T06:44:52.797Z WARN 1 --- [pool-5-thread-1] b.v.i.ldes.ldio.LdioLdesClient : HALTING pipeline because of an unhandled error
2024-08-20 08:44:52 2024-08-20T06:44:52.797Z ERROR 1 --- [pool-5-thread-1] b.v.i.ldes.ldio.LdioLdesClient : org.apache.http.conn.HttpHostConnectException: Connect to localhost:8082 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused
2024-08-20 08:44:52 2024-08-20T06:44:52.798Z INFO 1 --- [pool-5-thread-1] b.v.i.ldes.ldio.LdioLdesClient : UPDATED status for pipeline 'validation-pipeline' to HALTED
2024-08-20 08:46:26 2024-08-20T06:46:26.749Z WARN 1 --- [nio-8080-exec-9] o.s.web.servlet.PageNotFound : Request method 'GET' is not supported
2024-08-20 08:46:59 2024-08-20T06:46:59.975Z WARN 1 --- [nio-8080-exec-8] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: be.vlaanderen.informatievlaanderen.ldes.ldio.pipeline.web.PipelineController
2024-08-20 08:47:00 2024-08-20T06:47:00.304Z WARN 1 --- [nio-8080-exec-8] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: be.vlaanderen.informatievlaanderen.ldes.ldio.pipeline.status.web.PipelineStatusController
2024-08-20 08:47:00 2024-08-20T06:47:00.393Z WARN 1 --- [nio-8080-exec-8] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: be.vlaanderen.informatievlaanderen.ldes.ldio.management.status.ClientStatusController
Describe the bug When an error occures in the LDES Client, the pipeline gets HALTED. However, I would also expect to still be able to retrieve the ldes-client status, which would be ERROR in this case
Expected behavior Being able to retrieve the ldes client status ERROR when an error occures in the LDES Client
Screenshot
Logs