[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=16621922#comment-16621922
]
ASF subversion and git services commented on SYNCOPE-1374:
--
Commit 7c94b93a6755f06ece72ac052f156ab7e1d1c46d in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=7c94b93 ]
[SYNCOPE-1374] Removing unnecessary @Transactional
> 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)
[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=16621920#comment-16621920
]
ASF subversion and git services commented on SYNCOPE-1374:
--
Commit 43e07b3537489a60eba067a7f4deb1fc317c61bd in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=43e07b3 ]
[SYNCOPE-1374] Removing unnecessary @Transactional
> 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)
[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=16621921#comment-16621921
]
ASF subversion and git services commented on SYNCOPE-1374:
--
Commit cabb62b78ca8f96c67d11d72af8021990350e781 in syncope's branch
refs/heads/2_1_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=cabb62b ]
[SYNCOPE-1374] Removing unnecessary @Transactional
> 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)
[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=16621656#comment-16621656
]
ASF subversion and git services commented on SYNCOPE-1374:
--
Commit 23daf200a657dec48530be35b470a055da253c52 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=23daf20 ]
[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)
[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=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)
[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=16621655#comment-16621655
]
ASF subversion and git services commented on SYNCOPE-1374:
--
Commit 50e4b14c316ca416edfa3e26954bc539a966c03b in syncope's branch
refs/heads/2_1_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=50e4b14 ]
[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)
