Class AccountDeletionJob

java.lang.Object
io.meeds.social.security.job.AccountDeletionJob

@Configuration @EnableScheduling public class AccountDeletionJob extends Object
Job executing the account deletion requests whose grace delay elapsed: no business logic, it delegates the whole processing to AccountDeletionService. The container lifecycle is started here — the service is deliberately not transactional — and the service commits one transaction per processed account, so a failure never poisons the rest of the batch. There is no cluster lock either (Synchronized only prevents same-node overlaps): the processing is idempotent by construction — each account's request marker is removed within the same committed transaction as its deletion, so a replayed run finds nothing to do.
  • Constructor Details

    • AccountDeletionJob

      public AccountDeletionJob()
  • Method Details

    • run

      @Scheduled(cron="${exo.accountDeletion.job.expression:0 15 5 ? * *}") public void run()