smartBun opened a new issue #2019: URL: https://github.com/apache/shardingsphere-elasticjob/issues/2019
I expend a custom tracing configuration to record JobExecutionEvent, and JobTraceStatusEvent. and I met a problem. The job execute with an Runtime Exception at first time. So, I received a record with state JobStatusTraceEvent.State.TASK_ERROR, and some detail error message. It's worked expectly. And then, the job execute again successfully without any exception or error. But, I still received a record with state JobStatusTraceEvent.State.TASK_ERROR. And, the state and message is as same as first time run. I think, this is unexpectly. Is it a bug or if I misunderstood it? After that, I read the source code In file org.apache.shardingsphere.elasticjob.executorElasticJobExecutor.java I found that the ElasticJobExecutor.itemErrorMessages was initialed when job registed, and put message when catch a Throwable, But, the map is never cleared.  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
