You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2025/10/01 11:28:00 UTC
[jira] [Resolved] (SYNCOPE-1919) Notification Job occasionally stuck
[ https://issues.apache.org/jira/browse/SYNCOPE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1919.
---------------------------------------------
Resolution: Fixed
> Notification Job occasionally stuck
> -----------------------------------
>
> Key: SYNCOPE-1919
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1919
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 4.0.1
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 4.0.2, 4.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It was observed that the {{NotificationJob}} appears stuck (and not notifications are actually being sent out).
> The logs are showing
> {code}
> Could not lock job notificationJob, skipping execution
> {code}
> and
> {code}
> org.apache.openjpa.persistence.OptimisticLockException: Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [org.apache.syncope.core.persistence.jpa.entity.JPAJobStatus-systemLoadReporterJob]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)