You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Augustin Lafanechere (JIRA)" <ji...@apache.org> on 2019/03/15 11:38:00 UTC
[jira] [Commented] (BEAM-6843) RabbitMqIO:
com.rabbitmq.client.ShutdownSignalException - 406 PRECONDITION_FAILED
[ https://issues.apache.org/jira/browse/BEAM-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793559#comment-16793559 ]
Augustin Lafanechere commented on BEAM-6843:
--------------------------------------------
Sorry, duplicate of BEAM-6516
> RabbitMqIO: com.rabbitmq.client.ShutdownSignalException - 406 PRECONDITION_FAILED
> ----------------------------------------------------------------------------------
>
> Key: BEAM-6843
> URL: https://issues.apache.org/jira/browse/BEAM-6843
> Project: Beam
> Issue Type: Bug
> Components: io-java-rabbitmq
> Reporter: Augustin Lafanechere
> Priority: Major
>
> Using the RabbitMqIO as an unbounded source I encounter exceptions when messages are acknowledged.
> Reading the code of the IO I understood that ACK are sent when {{finalizeCheckpoint}} is called.
>
> If I understand the exception well, it's raised when messages are not acked in same order as they arrive to the system.
> Is there something I can do in my pipeline to avoid this exception ? Maybe something needs to be done on RabbitMQ side.
> Thanks for your help
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)