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

Posted to issues@camel.apache.org by "Christoph Deppisch (Jira)" <ji...@apache.org> on 2023/03/21 07:47:00 UTC

[jira] [Assigned] (CAMEL-19174) Jira component: duplicate messages with the new issues consumer

     [ https://issues.apache.org/jira/browse/CAMEL-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christoph Deppisch reassigned CAMEL-19174:
------------------------------------------

    Assignee: Christoph Deppisch

> Jira component: duplicate messages with the new issues consumer
> ---------------------------------------------------------------
>
>                 Key: CAMEL-19174
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19174
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jira
>    Affects Versions: 3.20.2, 4.0-M3
>         Environment: Also seen in Camel K environment with Jira source Kamelet
>            Reporter: Christoph Deppisch
>            Assignee: Christoph Deppisch
>            Priority: Critical
>
> When more than one JIRA issue fulfills the JQL and is available on a poll, it will result in  duplicates handled multiple times in the next poll. It depends on how many issues were created within the poll delay. Issues will be handled N times (N is the number of issues that were created at the same time).
> How to reproduce:
> - Make sure to return multiple issues for a JQL query
> - Wait multiple polls and review the resulting issues being handled by the Camel route



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