SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Service Broker is no longer able to send out messages!


Service Broker is no longer able to send out messages!

Author
Message
daniel.b.handy
daniel.b.handy
SSC Journeyman
SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)

Group: General Forum Members
Points: 80 Visits: 810
Hi All :-D,

Server 1: Server 2008 SP1, 10.0.2766 (SP1 CU7) - needs updating to , we know.
Server 2: Server 2003 SP2, 9.00.3042.00 (SP2 Vanilla) - needs updating, we know.

We’re seeing problems where service broker messages are not being propagated from the transmission queue on SERVER 1 over to SERVER 2. We are able to kick-start the flow of messages by dropping and creating the Service Broker endpoint on SERVER 1.

-- SERVER 1
USE MASTER;
DROP ENDPOINT ServiceBrokerEndpoint
GO
CREATE ENDPOINT ServiceBrokerEndpoint
AUTHORIZATION [sa]
STATE = STARTED
AS TCP ( LISTENER_PORT = 4022 )
FOR SERVICE_BROKER (
AUTHENTICATION = WINDOWS,
ENCRYPTION = DISABLED);
GO

GRANT CONNECT ON ENDPOINT::ServiceBrokerEndpoint TO PUBLIC;
GO

Further to this, It’s evident that a complete server reboot of SERVER 1 did not prevent this issue reoccurring. That is, we still have an issue where Service Broker for SERVER 1.XXXX appears to be no longer able to send out messages (however it is still able to accept incoming messages). We note that Service Broker sometimes wakes up and makes sporadic outbound connections but a point is reached where even this stops happening. We note also that dropping and recreating the (outbound) endpoint is enough to restart connections but not enough to ensure that they continue.

This is the sys table I've been watching that shows me when outbound TCP connections cease:

-- To prove that the endpoint is working, we should see two or three connections, inbound and outbound (is_accept =0 & =1)
select
t1.principal_name,
t1.last_activity_time,
t1.is_accept, -- 1= connections started remotely
t1.receives_posted, -- network receives that have not yet completed
t1.is_send_flow_controlled, -- 1= network sends have been postponed due to network flow control because the network is busy
t1.is_receive_flow_controlled, -- 1= network receives have been postponed due to flow control because the network is busy
t1.total_bytes_sent,
t1.total_bytes_received,
t1.total_fragments_sent, -- low!
t1.total_fragments_received,
t1.total_sends, -- low on both connections!
t1.total_receives,
t2.* from sys.dm_broker_connections t1
left outer join sys.dm_exec_connections t2 on t1.connection_id = t2.connection_id


Anyone have any thoughts about this one please?

Kind Regards,
Daniel.
Nils Gustav Stråbø
Nils Gustav Stråbø
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2433 Visits: 3575
What does message_body in sys.transmission_queue say?

Have you checked that routes are set up correctly on both servers? Make sure that service names (case sensitive), broker id and server names+ports are correct. Can you telnet the remote server + port from both servers? Try running a trace (including all broker events) on both servers to see if there is any communication between them. Any firewall blocking the ports you are using?
Nils Gustav Stråbø
Nils Gustav Stråbø
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2433 Visits: 3575
Another question.

Has it ever worked? If so, has anything changed between the time it worked to when it didn't work?
daniel.b.handy
daniel.b.handy
SSC Journeyman
SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)SSC Journeyman (80 reputation)

Group: General Forum Members
Points: 80 Visits: 810
Hi,

The configuration itself is fine and nothing has changed, its working at the moment but will just fail out of the blue.

Thanks,
Dan
sql server developer
sql server developer
Old Hand
Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)

Group: General Forum Members
Points: 364 Visits: 472
Hi Daniel,

I'm having same kind of issue with the below message. Did you come across this message when you were having trouble initiating the message from Server 1 in your example?

"A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State 116."

Thanks,
sql server developer
sql server developer
Old Hand
Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)Old Hand (364 reputation)

Group: General Forum Members
Points: 364 Visits: 472
Restarting SQL Server service on the initiator side fixed the issue.

Thanks so much everyone!!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search