Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: MessageRejectedWhileStoppingException while stopping

  1. #11
    Join Date
    Jun 2009
    Posts
    26

    Default

    Hi Gary
    I've just ran some tests and it appears to be ok.

    no. spring-rabbit version #messages #stop/starts #final result #unacked #failed
    A1 1.1.0.RELEASE 300000 73 300000 99 0
    B1 1.2.0.BUILD-SNAPSHOT 300000 71 300000 0 0
    B2 1.2.0.BUILD-SNAPSHOT 300000 63 300000 0 0

    can't wait for the final release of 1.2.0
    thanks buddy
    Last edited by nima; Nov 4th, 2012 at 03:26 AM.

  2. #12
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,039

    Default

    Thanks for letting us know; we will be back-porting this fix to the 1.1.x stream; 1.1.3 should be available later this week.
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

  3. #13
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,039

    Default

    spring-amqp 1.1.3.RELEASE, including this fix, is now available

    http://www.springsource.org/spring-amqp
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

  4. #14
    Join Date
    Jun 2009
    Posts
    26

    Default

    thanks buddy I really appreciate

  5. #15
    Join Date
    Apr 2013
    Posts
    2

    Default

    Hello,
    I have read through this post and something is still not clear to me. We have the same situation as the original poster. We send 300K test message in and we always get 300K out unless we stop a consumer. We then often get messages in the dead letter queue.

    Is it normal behavior to reject unacknowledged messages when a consumer shuts down via SimpleMessageListenerContainer.stop()? I would expect unacknowledged messages to go back to the queue. We do not want rejected messages to be requeued, we want them to go to the dead letter queue. Why are messages rejected on a clean stop request?

    TIA,
    Tracy

  6. #16
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,039

    Default

    Ouch; no, we shouldn't be rejecting deliveries for this exception. I assume you have 'defaultQueueRejected' set to true. The rejection code in this case does not filter out this exception.

    Please go ahead and open a JIRA issue.

    https://jira.springsource.org/browse/AMQP
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

  7. #17
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,039

    Default

    I have a fix, so I went ahead and opened a JIRA issue... https://jira.springsource.org/browse/AMQP-310
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

  8. #18
    Join Date
    Apr 2013
    Posts
    2

    Default

    Thanks Gary! So I understand correctly, messages that cannot be processed before stop is complete will be nacked rather than rejected?

  9. #19
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,039

    Default

    Correct; previously if you set defaultRequeuRejected=false (default is true) we always rejected the message (with requeue=false); now (when the fix is merged), we'll reject with requeue=true if the exception is simply because the container is in the process of stopping.
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •