Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8967243
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T17:11:56+00:00 2026-06-15T17:11:56+00:00

I have a distributor and 2 workers, in distributor’s storage queue messages are keep

  • 0

I have a distributor and 2 workers, in distributor’s storage queue messages are keep on increasing, each message has size of 2 kb.

I have gone through Udi reply here
http://tech.dir.groups.yahoo.com/group/nservicebus/message/10698
Messages are cleared from the distributor’s storage queue when it dispatches messages to the worker nodes.
That being said, the worker nodes usually send a ready message right afterwards, causing the storage queue to fill up again.

I am not clear about “causing the storage queue to fill up again.” Statement.

I was expecting max messages in distributor’s storage queue should be equal to number of workers but that is not the case.

Is there any configuration that I may be missing to control distributor’s storage queue clean up behavior?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T17:11:57+00:00Added an answer on June 15, 2026 at 5:11 pm

    As of NSB 3.3.2 there is an known issue, https://github.com/NServiceBus/NServiceBus/issues/806, with using SendLocal on worker in a distributor scenario. This will lead to the worker sending a “ready for a new message” every time it handles a message sent locally. This makes the distributors storage queue grow above the expected maximum of sum of all worker threads on all workers. This can be a problem if your sending lots of messages locally and the number of entries in the storage queue grows very large.

    Workarounds:

    1. Switch from SendLocal to Send
    2. Restart the workers(this will reset the storage, but it will build up again for every SendLocal on a worker

    There was also a similar issue with SLR(Second Level Retries) functionality( https://github.com/NServiceBus/NServiceBus/issues/571 ), but that was fixed in 3.2.7.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

If I have two tables - table beer and table distributor , each one
I have a large distributed program across many different physical servers, each program spawns
Let's say I have sj:autocompleter like this : <sj:autocompleter id=idDistributor name=idDistributor list=%{idDistributorList} label=ID Distributor
I have a distributed client server system which has multiple 'worker' engines and a
I have a merge replication scenario, with SQL2005 SP3 as the publisher and distributor
Json Problem : I have this formatted JSON { Table1:[ { TableName:LoadDistributor, Description:Distributor ,
(Before anyone asks, this is not homework.) I have a set of workers with
Background: I have a set of java background workers I start as part of
We have one distributor/publisher (NSB community version, which is on a domain but recently
I have a distributed C++ application, which is composed of 4 processes spread on

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.