Results 1 to 4 of 4

Thread: Limiting the number of non-ack messages for subsystem

  1. #1

    Default Limiting the number of non-ack messages for subsystem

    Hi,
    I am currently facing the following situation:
    My setup has a Topic Exchange, wherein all messages are stored. The problem is the messages consumed are limited by the backend-system. The backend-system is only able to process 10 message at the same time. Each of this messages is bound to separate thread and I need to wait for its execution. The execution time may vary between 10 seconds and 10 minutes. Is it reasonable to send ACKs just after this amount of time, for acceptance of new messages?

    During my research I found an article (http://dougbarth.github.com/2011/06/...n-a-leash.html), which faces a similar scenario. Could you help me, how to solve it with Spring and RabbitMQ?

    Thanks in advance!

  2. #2

    Default

    No one? :-(

    Solved it, thanks your help and patience. :-)
    Last edited by johanneshiemer; Oct 23rd, 2011 at 10:54 AM. Reason: Solution found.

  3. #3
    Join Date
    Jun 2005
    Posts
    4,241

    Default

    Care to share the details? I'm sure people will be interested in your use case and your solution.

  4. #4

    Default

    Hi Dave,
    of course I will. Have been in holidays and was not "allowed" to spent that much time at the evil side. :-)

    Solutions follows tomorrow.

Posting Permissions

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