All geek questions in one place

EndDialog messages stuck in a TARGET transmission queue with a session endpoint in DISCONNECTED_OUTBOUND state

EndDialog messages are stuck in the TARGET (remote) transmission queue. The transfer status is empty for each record.

The initiator actually receives the EndDialog message and terminates the dialog on it.

I know this for sure because I set PRINT to the INITIATOR service response queue procedure. The log shows that this procedure is performed as a result of the INITIATOR input receiving the EndDialog message.

Everything works, except that in TARGET, the conversation endpoint records remain in the DO state, and the EndDialog message also remains in the TARGET transmission queue.

It looks like TARGET is not getting the ACK from INITIATOR for the enddialog message.

In TARGET, the BROKER: CONVERSATION trace shows the STARTED_INBOUND, CONVERSING, DISCONNECTED_OUTBOUND states.

Follow the setup:

PURPOSE: Windows Server 2003 R2 Standard 64 edition SP2, SQL Server 2008 Service Pack 2, Standard 64-bit, Database in compatibility mode 100

INITIATOR: Windows XP SP2, SQL Server 2005 Express SP2, database in compatibility mode 80.

Do you have any recommendations for solving this problem?

0
source share
2 answers

Upgrading SQL Server Express from SP2 to SP4 resolved the issue. There are no more enddialog messages stuck in the destination transfer queue.

enddialog, - "ack". , .

, . , , , .

, , SQL Server Express SP4, .

, , .

0

ssbdiagnose . (, , ), , .

0

Source: https://habr.com/ru/post/1758889/

More articles:


All Articles