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/10/15 14:23:00 UTC
[jira] [Commented] (SYNCOPE-1385) Priority propagation timeout hard
coded into PriorityPropagationTaskExecutor
[ https://issues.apache.org/jira/browse/SYNCOPE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650284#comment-16650284 ]
ASF subversion and git services commented on SYNCOPE-1385:
----------------------------------------------------------
Commit 28812f7d168b054eae78909092fa42840dd97ef2 in syncope's branch refs/heads/2_0_X from fmartelli
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=28812f7 ]
[SYNCOPE-1385] makes PriorityPropagationTaskExecutor timeout closer to the maximum connector connection request timeout
> Priority propagation timeout hard coded into PriorityPropagationTaskExecutor
> ----------------------------------------------------------------------------
>
> Key: SYNCOPE-1385
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1385
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.0.10, 2.1.1
> Reporter: fabio martelli
> Assignee: fabio martelli
> Priority: Major
> Fix For: 2.0.11, 2.1.2, 3.0.0
>
>
> Waiting timeout for priority propagation is hard coded into PriorityPropagationTaskExecutor to 60 seconds. Since connectors can be configured to provide connection timeouts, it would be nice to have a timeout at least close to the maximum connection request timeout given for connectors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)