TeslaCN opened a new issue #1544:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1544
## Bug Report
### Which version of ElasticJob did you use?
3.0.0-alpha
### Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?
ElasticJob-Lite
### Reason analyze (If you can)
There is no listener is listening change of jobErrorHandlerType.
**Not only JobErrorHandler, the following interfaces also have this
problem:**
- JobExecutorServiceHandler
- ElasticJobListener
### Steps to reproduce the behavior.
1. Start a new process and schedule job 'simple' with job error handler type
'foo'.
2. Start another new process and schedule job 'simple' with job error
handler type 'bar'.
### Example codes for reproduce this issue (such as a github link).
Schedule 'simple' job with 'foo' error handler.
```java
new ScheduleJobBootstrap(REGISTRY_CENTER, new ErrorSimpleJob(),
JobConfiguration.newBuilder("simple", 3)
.cron("0/5 * * * * ?")
.shardingItemParameters("0=Beijing,1=Shanghai,2=Guangzhou")
.jobErrorHandlerType("foo")
.overwrite(true)
.build(),
TRACING_CONFIGURATION)
.schedule();
```
Schedule 'simple' job with 'bar' error handler.
```java
new ScheduleJobBootstrap(REGISTRY_CENTER, new ErrorSimpleJob(),
JobConfiguration.newBuilder("simple", 3)
.cron("0/5 * * * * ?")
.shardingItemParameters("0=Beijing,1=Shanghai,2=Guangzhou")
.jobErrorHandlerType("bar")
.overwrite(true)
.build(),
TRACING_CONFIGURATION)
.schedule();
```
### Expected behavior
All instances of 'simple' job use same error handler.
### Actual behavior
Node A using 'foo' error handler while Node B using 'bar' handler.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
