Multiple concurrent receivers #137

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
4 participants
@vadimskipin

Usage of Current / RemoveCurrent in MSMQ transport not look very safe, but what in theory: is there any reasons to not have multiple receivers? (And why not just use queue.Receive() like NSB?)

@phatboyg

This comment has been minimized.

Show comment Hide comment
@phatboyg

phatboyg Jul 9, 2012

Member

This can only be done with transactional queues, as non-transactional queues will fight over multiple receives. Have you actually tested this with multiple receivers in production and checked the logs for errors?

Member

phatboyg commented Jul 9, 2012

This can only be done with transactional queues, as non-transactional queues will fight over multiple receives. Have you actually tested this with multiple receivers in production and checked the logs for errors?

@vadimskipin

This comment has been minimized.

Show comment Hide comment
@vadimskipin

vadimskipin Jul 9, 2012

As I can remember queue was not transactional and test run was clean...
But this pull request is more question than suggestion so you can just ignore it.
All that I really want - is to understand MassThransit threading/concurrency architecture.

As I can remember queue was not transactional and test run was clean...
But this pull request is more question than suggestion so you can just ignore it.
All that I really want - is to understand MassThransit threading/concurrency architecture.

@TravisTheTechie

This comment has been minimized.

Show comment Hide comment
@TravisTheTechie

TravisTheTechie Jul 9, 2012

Contributor

What version of Windows/MSMQ are you running? It's possible they made this work, but multiple handles open to the queue used to become a problem sooner than with much less volume than a single handle. I could bring the machine to a halt at only around 100k messages in a queue.

What does having multiple receivers buy you, that you don't get with multiple consumers?

Contributor

TravisTheTechie commented Jul 9, 2012

What version of Windows/MSMQ are you running? It's possible they made this work, but multiple handles open to the queue used to become a problem sooner than with much less volume than a single handle. I could bring the machine to a halt at only around 100k messages in a queue.

What does having multiple receivers buy you, that you don't get with multiple consumers?

@drusellers

This comment has been minimized.

Show comment Hide comment
@drusellers

drusellers Mar 3, 2013

Member

Closing this pull request. No active conversation in 8 months and it seems it was more about asking a question. Thanks @vadimskipin for reaching out. :)

Member

drusellers commented Mar 3, 2013

Closing this pull request. No active conversation in 8 months and it seems it was more about asking a question. Thanks @vadimskipin for reaching out. :)

@drusellers drusellers closed this Mar 3, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment