Home Dashboard Directory Help
Search

Service Broker Initial connection fails if Route and Begin Dialog both include remote broker GUID by Heimir Sverrisson


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 778044
Opened: 1/31/2013 7:41:16 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I have set up Initiator and Target on separate servers.
All configuration passes ssbdiagnose on both servers with 0 issues.
On Initiator the route is defined as:

CREATE ROUTE [BirstTarget]
WITH
SERVICE_NAME = '//Birst/GPS/LocationService',
BROKER_INSTANCE = 'DE98C6BB-04FC-4B4A-B9E0-256B71A7FE3B',
ADDRESS = 'tcp://db-core:4037'
GO

When using the following code for the Dialog:

    BEGIN DIALOG CONVERSATION @handle     FROM SERVICE [//Birst/GPS/InitiatorLocationService]
        TO SERVICE '//Birst/GPS/LocationService', 'DE98C6BB-04FC-4B4A-B9E0-256B71A7FE3B'
        ON CONTRACT [//Birst/GPS/LocationContract]
        WITH ENCRYPTION =OFF ;

I see an error in SQL Profiler saying No Certificate followed by cannot create security context and the message is dropped!

By only removing the BROKER_INSTANCE from the ROUTE all is working fine:

CREATE ROUTE [BirstTarget]
WITH
SERVICE_NAME = '//Birst/GPS/LocationService',
ADDRESS = 'tcp://db-core:4037'
GO

I have not found any documentation saying that I cannot specify the GUID in both places so is this a bug?

The servers are running on VMWare.

/Heimir
Details
Sign in to post a comment.
Sign in to post a workaround.