[
https://issues.apache.org/jira/browse/SYNCOPE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024002#comment-18024002
]
ASF subversion and git services commented on SYNCOPE-1919:
----------------------------------------------------------
Commit 59909ffeb7d0b783fd7b292902c43631d36f8d38 in syncope's branch
refs/heads/4_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=59909ffeb7 ]
[SYNCOPE-1919] Ensuring that JobStatusUpdater can only update existing rows
(#1199)
> 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)
