Sign in
Microsoft.com
 
Microsoft
 
 
 

none
Does HPC R2's SessionStartInfo.BrokerSettingsInfo.ServiceOperationTimeout serve same role as HPC's client.InnerChannel.OperationTimeout? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    In HPC the client.InnerChannel.OperationTimeout setting needed to be adjusted to allow for long running SOA calls.

    In HPC R2, there is a property SessionStartInfo.BrokerSettingsInfo.ServiceOperationTimeout.

    Does this new property serve the same role to allow for long running SOA calls?

    Thanks!

    Wednesday, December 15, 2010 10:18 PM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Derek,

    SessionStartInfo.BrokerSettingsInfo.ServiceOperationTimeout is used to set the timeout to support long running SOA calls. Default value is 1 day.

    For the WCF client proxy as you mentioned, you still need to set client.InnerChannel.OperationTimeout to make it work.

    In HPC R2, we introduce BrokerClient to help you send/receive SOA calls. If you use this API, you will not need to set anything and it just works (if the calls are less than 1 day). If your SOA calls are longer than 1 day, you will need and only need to set SessionStartInfo.BrokerSettingsInfo.ServiceOperationTimeout for larger time period.

    • Marked as answer by Derek Kivi Thursday, December 16, 2010 4:29 PM
    Thursday, December 16, 2010 9:20 AM
    |