Currently the lock-timeout is hard-coded in EventTransmissionService.java. For applications it would be a benefit to adapt the configuration to their special needs. The current configuration should be kept as the default.
private boolean lockNearlyExpired(EventLog eventLog) {
// since clocks never work exactly synchronous and sending the event also takes some time, we include a minute
// of safety buffer here. This is still not 100% precise, but since we require events to be consumed idempotent,
// sending one event twice wont hurt much.
return now().isAfter(eventLog.getLockedUntil().minus(1, MINUTES));
}
Currently the lock-timeout is hard-coded in
EventTransmissionService.java
. For applications it would be a benefit to adapt the configuration to their special needs. The current configuration should be kept as the default.