WCF Transport Channel for SQL Server Service Broker

Created Issue: SQL Server 2012 is released, code update is needed. [33954]

Miron1 — Wed, 10 Apr 2013 16:44:27 GMT

Please update code for latest release of SQL Server.

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

New Post: Where is Microsoft SQL Server Service Team

vbsmerlin — Wed, 20 Jun 2012 16:40:48 GMT

It seems that once again Microsoft drops the ball on a program that has a lot of potential. At least they could have someone watch this post on codeplex and contribute to their own open source projects.

WCF Transport seems very good, but has a total lack to proper documentation. Service Broker itself is very poorly documented.

Microsoft please do something and help out the people that push your product.

Vince

New Post: Trouble implementing

pmbsa — Tue, 08 Feb 2011 08:21:20 GMT

Hi, I am not sure if this project is still alive, I am hoping so though. Please forgive the level of the questioning, I am very new to all things Microsoft.

I am in the middle of trying to prove I can make it work in a production environment (which it appears isnt being done yet which is a little concerning :))

I have gotten the test suite running beautifully which I am happy with and I have my head around the basics but when I try implement my own service I run into problems which I am hoping somebody may be able to help me with easily.

I have created a service broker service that listens on a Queue which expects simply well formed XML. I have created the binding for the servive but when I run the test in the command line

I get an encoder problem inside SsbInputSessionChannel. No matter what I put on the queue I get an error 'An XML declaration with an encoding is required for all non-UTF8 documents.'

when creating a Message Object (' Message message = this.encoder.ReadMessage(new ArraySegment<byte>(buffer, 0, messageLength), this.bufferManager);')

I am certain I am doing something stupid but for the life of me I cant seem to work it out.

any assistance would be appreciated right now! (as well as advice as to whether or not trying todo this in a prod environment is advisable)

thanks

Paul

Source code checked in, #74794

_TFSSERVICE — Tue, 03 Aug 2010 19:44:57 GMT

Checked in by server upgrade

New Post: Implementation

adisson — Mon, 09 Nov 2009 07:59:43 GMT

archnae wrote:

I stand corrected... WCF is amazinly extensible and with some subclassing of ServiceHost and tweaking app.config I've got a nice sql exceptions interceptor. All I have to do is to decide which ones are recoverable and how to recover from them except by recycling the ServiceHost. BTW, I've added "SenderEndsConversationAfterSendProperty" setting for shoot-and-forget scenarios - it saves the need to recycle the client proxy.

archnae can I get a copy of the code you wrote to capture the host errors. Are you resetting the SSSB queue?

New Post: Implementation

adisson — Mon, 09 Nov 2009 07:57:26 GMT

Hi guys,

Is there any updates at all on this? The post dates don't show the year so I cant asses if the last update on this was october 2009 or previous year.

This would be a very valuable addition to the WCF infrastructure specially a great candidate over the MSMQ binding to avoid the 4MB size limitation of queue messages.

10/11/2009

New Post: Implementation

dolson — Tue, 27 Oct 2009 06:42:04 GMT

Any one tested this with SSIS?

Actually right now am looking for a good solution to implement Service broker in our project....

We have a silverlight application which deals with huge data repository...

so sometimes we need to create the extract file from our prod Db, For that we are using SSIS.

My requirement is I need to integrate the SSIS execution with our silverlight Web app using service broker,

because i can use service broker queue for this....

Is that possible?

New Post: Is this project dead?

manishtpatel — Wed, 21 Oct 2009 19:10:12 GMT

I see no movement for last one year. As there is no release as well as no sign of any one working on it. Is it dead? or in progress?

Any other similar project Microsoft is working on?

New Post: Implementation

archnae — Wed, 24 Jun 2009 16:38:28 GMT

I stand corrected... WCF is amazinly extensible and with some subclassing of ServiceHost and tweaking app.config I've got a nice sql exceptions interceptor. All I have to do is to decide which ones are recoverable and how to recover from them except by recycling the ServiceHost. BTW, I've added "SenderEndsConversationAfterSendProperty" setting for shoot-and-forget scenarios - it saves the need to recycle the client proxy.

New Post: Implementation

archnae — Mon, 22 Jun 2009 11:56:15 GMT

Well, I tried to use it with an eye on going to production. So far there are 2 big problems:

It's impossible to configure a Ssb endpoint in the config file (WCF complains about the parentage of the SsbBindingElement);
If an exception is thrown the queue could be disabled as a result. It is a "normal" mode of operation for Service Broker Queues, but with WCF such exceptions are mostly silently swallowed (it is a one way protocol, after all), so there is no visible indicators at all. I'd say David should add an event on the host to handle "something bad happened" situations. It applies also to the case when the queue was disabled from the start. The .exe running the ServiceHost is not ever informed about it.

(2) is more-or-less expected in Service Broker Queue apps, but WCF adds an extra layer of mystery between "real" errors and what the container do (or doesn't) see. If the container is a minimalistic Windows service knowing nothing about what services are run inside it (it's all supposed to be in the config file) and about contracts they are exposing, it can not even check for possible error conditions. It means that the burden of checking for database errors goes to the services... but they don't know they are published via Ssb.

Give me a stupid but 100% reliable way to report errors in the production environment... if we can't report them to the client, at least report them to the host.

Alexander

Created Issue: produces "...SsbBindingElement is not inherited from BindingElementExtensionElement" error.

archnae — Mon, 22 Jun 2009 11:37:56 GMT

SsbBindingElement is inherited from the TransportBindingElement, but WCF wants extension elements to be BindingElementExtensionElement, and says so.

It means that there is no way to completely configure Ssb endpoint in the configuration file.

New Post: Implementation

dbrowne — Thu, 12 Mar 2009 18:28:12 GMT

Yes, the main benefit of SSB over MSMQ is that the data is stored in the databsae. There is no built-in support for pub/sub in Service Broker or WCF, but you could certianly build a pub/sub solution on top of this.

What's there is the current version of the code.

David

New Post: Implementation

adisson — Thu, 12 Mar 2009 18:16:58 GMT

Hi,

I'd like to use this as a replacement for the MSMQ binding to obtain durable storage. Transactional queues are stored in the file system and do not provide a great way for recovery after a server failure. So database would solve that issue.

My intention is to create this as a generic pub sub service. Do you have a more recent version of the code? Do you think this would work for this purpose?

New Post: Implementation

dbrowne — Wed, 11 Feb 2009 23:01:59 GMT

No one has yet put it into production and told me about it. I can offer guidance in validating whether it will work in your scenario and advice if you run into problems implementing it.

New Post: Implementation

tdev — Wed, 11 Feb 2009 22:47:56 GMT

Has anyone tried this yet?

Source code checked in, #38834

dbrowne — Wed, 03 Sep 2008 21:46:05 GMT

Source code checked in, #38832

dbrowne — Wed, 03 Sep 2008 21:39:46 GMT

Source code checked in, #35053

dbrowne — Wed, 06 Aug 2008 19:12:04 GMT