[
https://issues.apache.org/jira/browse/SYNCOPE-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409359#comment-16409359
]
ASF subversion and git services commented on SYNCOPE-1285:
----------------------------------------------------------
Commit 47657b51d2e3f28cb130628082bb0d1664e7111d in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=47657b5 ]
[SYNCOPE-1285] Now performing Quartz db init only if table QRTZ_SCHEDULER_STATE
is not found
> Quartz db init on HA environments occurs on all nodes
> -----------------------------------------------------
>
> Key: SYNCOPE-1285
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1285
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.8
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Labels: quartz
> Fix For: 2.0.9, 2.1.0
>
>
> Quartz database initialization - which currently involves dropping and
> creating several {{QRTZ_}} tables - is executed at startup, regardless of the
> fact that tables are already present.
> This can lead to problematic situations, especially in HA environments, where
> the quartz tables might get dropped by node2 startup while node1 is actually
> running a job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
