November 10, 2008 at 6:52 pm
Thank you for the advice. What I have done is similar adding an else statement and adding a xp_logevent call to not that the queue identifier is undefined. What is even more confusing is that when I exec the sender there is a single entry in the log file indicating that the conversation_handle is null. But subsequent executions of the sender show no activation of the stored procedure. It seems irrational that it would active the procedure once but then stop any further execution.
November 10, 2008 at 9:26 pm
Can you post the current version of the code?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
November 10, 2008 at 9:44 pm
How big is the Sales table? Is it possible that it is INSERTing into the Sales table but with unexpected values so that it is getting lost?
Also, have you checked the Queue status and Activation status to make sure that they are both still enabled (poison message handling turns one of these off under certain circumstances).
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
November 11, 2008 at 11:49 am
Thank-you for all of the help. I believe that I have figured out the problem. I was using different contract names in the sender and reciever databases. I made those consistent and a couple of other tweaks and the databases are now communicating via the service broker.
November 11, 2008 at 12:14 pm
That's Great! Glad it worked out and thanks for the feedback.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
August 1, 2011 at 4:29 am
I am using server broker. It was wroking fine since last one month but all of sudden it has stopped sending all the messages to target. Some of the messages are get passed through but some are remaining in source sys.transmission_queue. In transmission_status Column I am getting 'blank' value. Sometime I get message 'Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.' but after some time these message are getting cleared from the transmission_queue.
This is very unusual behaviour of the service broker.
Help on this would be really appriciated.
Thanks,
Vinod Patwal
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply