RabbitMQ best practice to handle exceptions when process a message asynchronously










0















Registered a async consumer of rabbitmq message.
Didn't get official suggestions how to handle the process exception in async consumer action?

Maybe need retry the queue message /republish the message to the queue with a retry times limitation.










share|improve this question


























    0















    Registered a async consumer of rabbitmq message.
    Didn't get official suggestions how to handle the process exception in async consumer action?

    Maybe need retry the queue message /republish the message to the queue with a retry times limitation.










    share|improve this question
























      0












      0








      0








      Registered a async consumer of rabbitmq message.
      Didn't get official suggestions how to handle the process exception in async consumer action?

      Maybe need retry the queue message /republish the message to the queue with a retry times limitation.










      share|improve this question














      Registered a async consumer of rabbitmq message.
      Didn't get official suggestions how to handle the process exception in async consumer action?

      Maybe need retry the queue message /republish the message to the queue with a retry times limitation.







      rabbitmq






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 '18 at 2:14









      cc5zhenhuacc5zhenhua

      75215




      75215






















          1 Answer
          1






          active

          oldest

          votes


















          0














          When consuming from a queue in rabbitMq you can set an option called noAck that can be true or false.




          • true it will ack a message in the event of an error it cannot handle


          • false will automatically nack the message and will stay in the
            queue to be pulled later.

          (This will depend on the language you are using for your consumer. noAck = nodejs, autoAck = c#, etc.)



          consumer.consume(q.queue, function (message) 
          // your code
          , noAck: false);


          In regards to setting limited retries, I had to do this myself by passing the retry count in the header of the message I was passing and had to ack the message I was reading before sending the new version with the modified header back to the queue. I used multiple queues in order to maintain message integrity but this could be done with one queue.



          I hope this has helped.






          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292232%2frabbitmq-best-practice-to-handle-exceptions-when-process-a-message-asynchronousl%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            When consuming from a queue in rabbitMq you can set an option called noAck that can be true or false.




            • true it will ack a message in the event of an error it cannot handle


            • false will automatically nack the message and will stay in the
              queue to be pulled later.

            (This will depend on the language you are using for your consumer. noAck = nodejs, autoAck = c#, etc.)



            consumer.consume(q.queue, function (message) 
            // your code
            , noAck: false);


            In regards to setting limited retries, I had to do this myself by passing the retry count in the header of the message I was passing and had to ack the message I was reading before sending the new version with the modified header back to the queue. I used multiple queues in order to maintain message integrity but this could be done with one queue.



            I hope this has helped.






            share|improve this answer



























              0














              When consuming from a queue in rabbitMq you can set an option called noAck that can be true or false.




              • true it will ack a message in the event of an error it cannot handle


              • false will automatically nack the message and will stay in the
                queue to be pulled later.

              (This will depend on the language you are using for your consumer. noAck = nodejs, autoAck = c#, etc.)



              consumer.consume(q.queue, function (message) 
              // your code
              , noAck: false);


              In regards to setting limited retries, I had to do this myself by passing the retry count in the header of the message I was passing and had to ack the message I was reading before sending the new version with the modified header back to the queue. I used multiple queues in order to maintain message integrity but this could be done with one queue.



              I hope this has helped.






              share|improve this answer

























                0












                0








                0







                When consuming from a queue in rabbitMq you can set an option called noAck that can be true or false.




                • true it will ack a message in the event of an error it cannot handle


                • false will automatically nack the message and will stay in the
                  queue to be pulled later.

                (This will depend on the language you are using for your consumer. noAck = nodejs, autoAck = c#, etc.)



                consumer.consume(q.queue, function (message) 
                // your code
                , noAck: false);


                In regards to setting limited retries, I had to do this myself by passing the retry count in the header of the message I was passing and had to ack the message I was reading before sending the new version with the modified header back to the queue. I used multiple queues in order to maintain message integrity but this could be done with one queue.



                I hope this has helped.






                share|improve this answer













                When consuming from a queue in rabbitMq you can set an option called noAck that can be true or false.




                • true it will ack a message in the event of an error it cannot handle


                • false will automatically nack the message and will stay in the
                  queue to be pulled later.

                (This will depend on the language you are using for your consumer. noAck = nodejs, autoAck = c#, etc.)



                consumer.consume(q.queue, function (message) 
                // your code
                , noAck: false);


                In regards to setting limited retries, I had to do this myself by passing the retry count in the header of the message I was passing and had to ack the message I was reading before sending the new version with the modified header back to the queue. I used multiple queues in order to maintain message integrity but this could be done with one queue.



                I hope this has helped.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 14 '18 at 7:11









                Chris BattenChris Batten

                1




                1



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292232%2frabbitmq-best-practice-to-handle-exceptions-when-process-a-message-asynchronousl%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Top Tejano songwriter Luis Silva dead of heart attack at 64

                    ReactJS Fetched API data displays live - need Data displayed static

                    政党