Service broker in disabled or stopped state

Windows Query 6

Previously, AlwaysOn group didn't have a listener set up. One was set up recently been getting service broker is in disabled or stopped state every 15 minutes.

Went through multiple forums and articles and nothing seems to stick out. Some say its by design (I mean every 15 minutes?). I don't see those messages every 15 minutes on other alwaysOn SQL servers.

Erland Sommarskog 118.9K Reputation points MVP

2020-11-04T22:55:26.687+00:00

Can you post the exact error message? Where do you see it?

Did you ever have Service Broker running on this AG?

Do to you use Service Broker on the AGs where you don't see this message?
Windows Query 6 Reputation points

2020-11-17T20:42:35.123+00:00

The exact message is "The Service Broker endpoint is in disabled or stopped state" and occurs every 15 minutes.
There is no service broker endpoint in the AG. This AG didn't have a group listener and application pointed to it through cluster address. When AG listener was created this started popping up.

I see that some of the databases in AG have service broker set to true whereas some have it set to false. So, options are to remove the databases out of AG and set them to false (which would cause application outage) OR to create service broker endpoint? I keep reading that service broker endpoint needs to be created first before AG. So, not sure what that will break if that is created.
Erland Sommarskog 118.9K Reputation points MVP

2020-11-17T22:04:45.357+00:00

The endpoints are created by server in the AG, but to handle incoming traffic, you also need to involve the listener. It was too long since I dealt with that, so I don't remember exactly.

While you certainly could create endpoint in the servers for your AG, that is maybe not the best of ideas, since you don't know is happening next. Maybe you should look around in sys.transmission_queue in all databases (including msdb!)to see if there is anything queued. Alternatively, use Profiler with all Broker events enabled to see from which database the activity is coming from.

1 answer

Cris Zhan-MSFT 6,646 Reputation points

2020-11-05T08:40:33.747+00:00

Hi @Windows Query ,

I can see this message in the SQL Server error log in my Always On availability group with listener configured(but not frequently). Usually this should be a message that can be ignored.

But this message appears every 15 minutes in your case , so i read some posts taliking about this , and they pointed a way is to configure the Service Broker endpoint for the SQL Server instances in AOAG. Try to test in a test environment.
https://feedback.azure.com/forums/908035-sql-server/suggestions/32907967-alwayson-the-service-broker-endpoint-is-in-disab

http://slavasql.blogspot.com/2019/11/errorlog-flooded-with-service-broker.html

If the answer is helpful, please click "Accept Answer" and upvote it.
Hot issues in October—Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet
Please sign in to rate this answer.
Windows Query 6 Reputation points

2020-11-17T20:44:49.677+00:00

thank you. The first link you provided has a lot of back and forth type of Q&As and doesn't quite answer . The second link talks about creating a service broker endpoint in test. The thing is MS documents talks about creating service broker endpoint before the AG is created. So, not sure what that will break.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Service broker in disabled or stopped state

1 answer

Your answer