Results 1 to 3 of 3

Thread: Best Practices and Recover a Faulted Channel

  1. #1
    Join Date
    May 2009
    Posts
    1

    Default Best Practices and Recover a Faulted Channel

    Hi.

    I have a question.
    Sometimes our WCF net.tcp binded service falls in faulted mode.
    For the moment to get a new working connection, we have to restart the client app.... Not very nice.

    How do you recover from this state using spring and wcf ? For the moment we're using the client proxy in singleton mode. This was the only way we've found to avoid a second problem. The second problem being we don't know how to close a channel, and after a certain time od use we exceed the default (10) number of channel allowed.

    Thanks for your help.

  2. #2
    Join Date
    Aug 2005
    Location
    Tampere, Finland
    Posts
    159

    Default

    Hi,

    Singleton WCF proxy sounds like a bad idea. The proxy channel can get in a faulted state and is no longer usable then. There's some discussion at least here:

    http://stackoverflow.com/questions/5...ng-block-issue

    Generally it's advisable to have some kind of template to wrap WCF calls to prevent misuse.

    Cheers,

    -Marko

  3. #3
    Join Date
    Oct 2005
    Location
    Belgium
    Posts
    213

    Default

    I've been busy with that, check it out here.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •