[
https://issues.apache.org/jira/browse/SYNCOPE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053401#comment-17053401
]
ASF subversion and git services commented on SYNCOPE-1546:
----------------------------------------------------------
Commit 9aba7838c85bf16163d1d43841793112c6b346ba in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=9aba783 ]
[SYNCOPE-1546] Ensuring rejected propagation tasks are stored if configured +
adding report metrics for asyncConnectorExecutor and asyncConnectorExecutor
> PriorityPropagationTaskExecutor: rejected tasks not stored
> ----------------------------------------------------------
>
> Key: SYNCOPE-1546
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1546
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.14, 2.1.5
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 2.1.6, 3.0.0
>
>
> {{PriorityPropagationTaskExecutor}} internally uses a
> [CompletionService|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ExecutorCompletionService.html]
> instance to run non-priority propagation tasks in parallel.
> Such {{CompletionService}} is baked by a {{ThreadPoolTaskExecutor}} which
> might reject tasks, depending on the allocated resources.
> In such cases the rejected propagation tasks are not stored, regardless of
> the settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
