You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/09/20 08:24:00 UTC

[jira] [Commented] (SYNCOPE-1374) Concurrent propagation tasks for non-Master domains not saved

    [ https://issues.apache.org/jira/browse/SYNCOPE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621654#comment-16621654 ] 

ASF subversion and git services commented on SYNCOPE-1374:
----------------------------------------------------------

Commit 16938c73b373dcb9d803c566349a812f437de8b4 in syncope's branch refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=16938c7 ]

[SYNCOPE-1374] Ensuring Spring can correctly inject the actual Domain


> Concurrent propagation tasks for non-Master domains not saved
> -------------------------------------------------------------
>
>                 Key: SYNCOPE-1374
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1374
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.10, 2.1.1
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> When executing concurrent propagations (e.g. for null-priority External Resources) for domains other than Master, the related {{PropagationTask}} is not saved, even if trace settings are configured in that way.
> The problem seems to be related to an incorrect reference to Master's JPA Persistence Unit, which makes OpenJPA attempting to save against the wrong database.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)