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 2023/02/01 14:46:02 UTC

[jira] [Commented] (SYNCOPE-1726) WA does not always get configuration from Core on startup

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

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

Commit eaad1f0f2a3a38bef705f917bd0014f758f701f7 in syncope's branch refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=eaad1f0f2a ]

[SYNCOPE-1726] Ensuring Core and calling WA instance are both available in Keymaster before refreshing


> WA does not always get configuration from Core on startup
> ---------------------------------------------------------
>
>                 Key: SYNCOPE-1726
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1726
>             Project: Syncope
>          Issue Type: Bug
>          Components: wa
>    Affects Versions: 3.0.1
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 3.0.2, 4.0.0
>
>
> Sometimes it happens, especially when using Self Keymaster and WA and Core are deployed together within the same JavaEE container instance, that all seems to start successfully yet WA shows no configuration from Core.
> In such cases, pushing the configuration resolves the situation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)