Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Service Broker is no longer able to send out messages! Expand / Collapse
Author
Message
Posted Tuesday, October 18, 2011 7:59 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:10 PM
Points: 24, Visits: 810
Hi All ,

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.
Post #1192081
Posted Tuesday, October 18, 2011 9:13 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 4:51 AM
Points: 1,854, Visits: 3,451
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?
Post #1192188
Posted Tuesday, October 18, 2011 9:14 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 4:51 AM
Points: 1,854, Visits: 3,451
Another question.

Has it ever worked? If so, has anything changed between the time it worked to when it didn't work?
Post #1192194
Posted Tuesday, October 18, 2011 9:47 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:10 PM
Points: 24, 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
Post #1192247
Posted Thursday, November 10, 2011 2:16 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: 2 days ago @ 11:25 PM
Points: 151, Visits: 428
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,
Post #1203836
Posted Friday, November 25, 2011 11:06 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: 2 days ago @ 11:25 PM
Points: 151, Visits: 428
Restarting SQL Server service on the initiator side fixed the issue.

Thanks so much everyone!!
Post #1212089
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse