Problem With ServiceBroker

Dec 29, 2005

I use 2 SQL Server: 1 €“ SQL Server 2005 Enterprise on Windows Server 2003 (Itanium) and SQL Server Express on Windows XP Professional (Pentium).

I send the message from enterprise to express the message (at once I shall tell, that sending of the message in the opposite direction gives the same result) and I process the message on express. At first sight like all is correct. Messages I receive all, I read also all of them are correct. But further there are two strange things for me.

In the table sys.conversation_endpoints there is a record (one, irrespective of how many messages in one conversation) with €śstate=CD€?. I read that they should be deleted after 30 minutes, but they did not. Using command €¦ WITH CLEANUP helps but in a parallel way in Service Broker Profiler I observe occurrence of a mistake which occurs after closing dialogue.

I am disturbed with this mistake and the most important is that I not understand why it arises.







EXPRESS



Event Class


EventSubClass


TextData



Broker:Message Classify


1 - Local






Broker:Conversation Group


1 - Create






Broker:Conversation


12 - Dialog Created


STARTED_INBOUND



Broker:Conversation


6 - Received Sequenced Message


CONVERSING



Broker:Remote Message Acknowledgement


3 - Message with Acknowledgement Received






Broker:Conversation


6 - Received Sequenced Message


CONVERSING



Broker:Remote Message Acknowledgement


3 - Message with Acknowledgement Received






Broker:Conversation


7 - Received END CONVERSATION


DISCONNECTED_INBOUND



Broker:Remote Message Acknowledgement


3 - Message with Acknowledgement Received






Broker:Activation


1 - Start






Broker:Message Classify


2 - Remote






Broker:Remote Message Acknowledgement


2 - Acknowledgement Sent






Broker:Conversation


2 - END CONVERSATION


CLOSED



Broker:Conversation Group









Broker:Activation


2 - Ended






Broker:Connection


4 - Closing


An error occurred while receiving data: '64(error not found)'.



Broker:Connection


5 - Closed








Enterprise



Event Class


EventSubClass


TextData



Broker:Conversation Group


1 - Create






Broker:Conversation


11 - BEGIN DIALOG


STARTED_OUTBOUND



Broker:Conversation


1 - SEND Message


CONVERSING



Broker:Message Classify


2 - Remote






Broker:Conversation


1 - SEND Message


CONVERSING



Broker:Message Classify


2 - Remote






Broker:Conversation


1 - SEND Message


CONVERSING



Broker:Message Classify


2 - Remote






Broker:Conversation


2 - END CONVERSATION


DISCONNECTED_OUTBOUND



Broker:Conversation Group


2 - Drop






Broker:Message Classify


2 - Remote






Broker:Message Classify


2 - Remote






Broker:Remote Message Acknowledgement


1 - Message with Acknowledgement Sent






Broker:Remote Message Acknowledgement


1 - Message with Acknowledgement Sent






Broker:Remote Message Acknowledgement


1 - Message with Acknowledgement Sent






Broker:Message Classify


1 - Local






Broker:Conversation


10 - Received END CONVERSATION Ack


CLOSED



Broker:Remote Message Acknowledgement


4 - Acknowledgement Received






Broker:Connection


4 - Closing






Broker:Connection


5 - Closed




 

Yours faithfully,

View 1 Replies


ADVERTISEMENT

If WCF Can Communicate With ServiceBroker?

Dec 10, 2006

hi,

I want tomake wcf and service broker communicate with each other,Are there some resources about that?

thanks in advance

View 10 Replies View Related

ServiceBroker And Express Edition

Mar 7, 2006

Is Service Broker available for express edition?

View 4 Replies View Related

ServiceBroker Error 8490 - SqlCacheDependency Not Invalidated

Sep 22, 2006

SQL Server 2005 / .NET 2.0 Web App - SqlCacheDependency is not invalidated and I see an error sql log that occurs after the specified table changes:



2006-09-22 12:18:51.84 spid21s The query notification dialog on
conversation handle '{8D7EF5BC-544A-DB11-B6E0-000F1FD735BF}.' closed
due to the following error: '<?xml version="1.0"?><Error
xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot
find the remote service
&apos;SqlQueryNotificationService-d61fa581-0567-43ba-991f-37499e87cbf6&apos;
because it does not exist.</Description></Error>'.

I've read all applicable articles that I can find and applied hotfix kb916002. The sqldependency has never worked, it is not a stability issue as described in kb916002. In a trace I can see the sqldependency starts correctly. I have a console app that works fine with SqlDependancy calling same database and login creds. I don't know what to think. Calling sys.dm_qn_subscriptions show no subscriptions when this app starts as does the console app. Please advise as it looks like a broker issue.

Thanks

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved