SQL ServiceBroker Error “A previously existing connection with the same peer was found after DNS lookup”...
up vote
1
down vote
favorite
Service broker messages between our two servers have suddenly ceased working with multiple messages being written to sys.transmission_queue stating:
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.
Both servers publish and receive messages to each other but nothing is flowing between the two.
Server A is writing multiple entries to the
transmission_queuebut does not populate the transmission status with any value.Server B is also writing multiple entries but populates the status with the above message.
Traces have so far revealed nothing and this has only started occurring in the last few days.
The only solutions I can find suggested online are to restart the SQL instances but that seems drastic.
Any suggestions would be welcome!
sql-server service-broker edited Nov 19 at 13:47
TT.
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
Service broker messages between our two servers have suddenly ceased working with multiple messages being written to sys.transmission_queue stating:
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.
Both servers publish and receive messages to each other but nothing is flowing between the two.
Server A is writing multiple entries to the
transmission_queuebut does not populate the transmission status with any value.Server B is also writing multiple entries but populates the status with the above message.
Traces have so far revealed nothing and this has only started occurring in the last few days.
The only solutions I can find suggested online are to restart the SQL instances but that seems drastic.
Any suggestions would be welcome!
sql-server service-broker edited Nov 19 at 13:47
TT.
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Service broker messages between our two servers have suddenly ceased working with multiple messages being written to sys.transmission_queue stating:
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.
Both servers publish and receive messages to each other but nothing is flowing between the two.
Server A is writing multiple entries to the
transmission_queuebut does not populate the transmission status with any value.Server B is also writing multiple entries but populates the status with the above message.
Traces have so far revealed nothing and this has only started occurring in the last few days.
The only solutions I can find suggested online are to restart the SQL instances but that seems drastic.
Any suggestions would be welcome!
sql-server service-broker edited Nov 19 at 13:47
TT.
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Service broker messages between our two servers have suddenly ceased working with multiple messages being written to sys.transmission_queue stating:
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.
Both servers publish and receive messages to each other but nothing is flowing between the two.
Server A is writing multiple entries to the
transmission_queuebut does not populate the transmission status with any value.Server B is also writing multiple entries but populates the status with the above message.
Traces have so far revealed nothing and this has only started occurring in the last few days.
The only solutions I can find suggested online are to restart the SQL instances but that seems drastic.
Any suggestions would be welcome!
sql-server service-broker sql-server service-broker edited Nov 19 at 13:47
TT.
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 19 at 13:47
TT.
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 19 at 13:47
TT.
12.1k63161
edited Nov 19 at 13:47
TT.
12.1k63161
edited Nov 19 at 13:47
TT.
12.1k63161
12.1k63161
asked Nov 19 at 12:18
Rich
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 19 at 12:18
Rich
61
asked Nov 19 at 12:18
Rich
61
61
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Rich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30
add a comment |
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Rich is a new contributor. Be nice, and check out our Code of Conduct.
Rich is a new contributor. Be nice, and check out our Code of Conduct.
Rich is a new contributor. Be nice, and check out our Code of Conduct.
Rich is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374474%2fsql-servicebroker-error-a-previously-existing-connection-with-the-same-peer-was%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I see that same message in my error logs all the time and I treat it as benign. Which doesn't help you solve your problem. Where I'd start though is an extended events session for one of the affected conversation handles. Which event? Hard to say. Search for "broker" in the extended events dialog. Make sure that you have all of the channels enabled!
– Ben Thul
Nov 19 at 21:30