Styjun

Do living authors still get paid royalties for their old work?

Have only girls been born for a long time in this village?

Would it be illegal for Facebook to actively promote a political agenda?

Chess software to analyze games

Why would the President need briefings on UFOs?

Unbiased estimator of exponential of measure of a set?

In xXx, is Xander Cage's 10th vehicle a specific reference to another franchise?

iPhone 8 purchased through AT&T change to T-Mobile

How could Tony Stark wield the Infinity Nano Gauntlet - at all?

Using は before 欲しい instead が

Is there such a thing as too inconvenient?

What can I do to keep a threaded bolt from falling out of it’s slot

Does C++20 mandate source code being stored in files?

Church Booleans

What professions does medieval village with a population of 100 need?

Nuclear decay triggers

Earliest evidence of objects intended for future archaeologists?

How do you call it when two celestial bodies come as close to each other as they will in their current orbits?

Did the twin engined Lazair ultralight have a throttle for each engine?

What is the latest version of SQL Server native client that is compatible with Sql Server 2008 r2

Count the frequency of items in an array

"Silverware", "Tableware", and "Dishes"

How to dismiss intrusive questions from a colleague with whom I don't work?

Is a butterfly one or two animals?

WCF NetTcpBinding Streaming limited to single Channel instance

NetTcpBinding with Streaming and SessionWCF NetTcpBinding + Single Instance + Single Concurrency = Blocking/Dropping Calls?WCF Throttling with Multiple ServiceContractsHow does WCF instance workHave a single connection with netTcpBinding between client and WCF serviceHow to stream file in WCF using NetTcpBinding? (got exception)Is Concurrency mode relevent if we use PerCall instancing?Catch-22 prevents streamed TCP WCF service securable by WIF; ruining my Christmas, mental healthWcf Singleton with Single ThreadNetTcpBinding and async/await WCF blocking

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

I have a self hosted WCF server which is configured using a NetTcpBinding.

The Service and Contract are set up with:

• SessionMode: Allowed


• InstanceContextMode: PerCall


• ConcurrencyMode: Multiple

The TcpTransport is set up as Streamed

I've implemented a IChannelInitializer to implement a rudimentary counter.

However, it appears that the IChannelInitializer only ever gets called once.

If I change the Transport to Buffered then the IChannelInitializer gets called for every request.

According to this article:

You may get unexpected behavior when streaming calls with a session-based binding. All streaming calls are made through a single channel (the datagram channel) that does not support sessions even if the binding being used is configured to use sessions. If multiple clients make streaming calls to the same service object over a session-based binding and the service object's concurrency mode is set to single and its instance context mode is set to PerSession, all calls must go through the datagram channel and so only one call is processed at a time. One or more clients may then time out. You can work around this issue by either setting the service object's Instance Context Mode to PerCall or Concurrency to Multiple.

So shouldn't PerCall be ensuring an instance is created for each call, as per the final sentence?

Am I using Sessions? My client creates an instance of a Proxy for each call, so I wouldn't expect session behaviour.

c# wcf wcf-binding nettcpbinding

share|improve this question

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I think you have to explicitly turn off session support. Try SessionMode = SessionMode.NotAllowed.
  
  – Clay
  Mar 28 at 21:50
  

  
  
  
  

add a comment | 

0

I have a self hosted WCF server which is configured using a NetTcpBinding.

The Service and Contract are set up with:

• SessionMode: Allowed


• InstanceContextMode: PerCall


• ConcurrencyMode: Multiple

The TcpTransport is set up as Streamed

I've implemented a IChannelInitializer to implement a rudimentary counter.

However, it appears that the IChannelInitializer only ever gets called once.

If I change the Transport to Buffered then the IChannelInitializer gets called for every request.

According to this article:

You may get unexpected behavior when streaming calls with a session-based binding. All streaming calls are made through a single channel (the datagram channel) that does not support sessions even if the binding being used is configured to use sessions. If multiple clients make streaming calls to the same service object over a session-based binding and the service object's concurrency mode is set to single and its instance context mode is set to PerSession, all calls must go through the datagram channel and so only one call is processed at a time. One or more clients may then time out. You can work around this issue by either setting the service object's Instance Context Mode to PerCall or Concurrency to Multiple.

So shouldn't PerCall be ensuring an instance is created for each call, as per the final sentence?

Am I using Sessions? My client creates an instance of a Proxy for each call, so I wouldn't expect session behaviour.

c# wcf wcf-binding nettcpbinding

share|improve this question

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I think you have to explicitly turn off session support. Try SessionMode = SessionMode.NotAllowed.
  
  – Clay
  Mar 28 at 21:50
  

  
  
  
  

add a comment | 

I have a self hosted WCF server which is configured using a NetTcpBinding.

The Service and Contract are set up with:

• SessionMode: Allowed


• InstanceContextMode: PerCall


• ConcurrencyMode: Multiple

The TcpTransport is set up as Streamed

I've implemented a IChannelInitializer to implement a rudimentary counter.

However, it appears that the IChannelInitializer only ever gets called once.

If I change the Transport to Buffered then the IChannelInitializer gets called for every request.

According to this article:

You may get unexpected behavior when streaming calls with a session-based binding. All streaming calls are made through a single channel (the datagram channel) that does not support sessions even if the binding being used is configured to use sessions. If multiple clients make streaming calls to the same service object over a session-based binding and the service object's concurrency mode is set to single and its instance context mode is set to PerSession, all calls must go through the datagram channel and so only one call is processed at a time. One or more clients may then time out. You can work around this issue by either setting the service object's Instance Context Mode to PerCall or Concurrency to Multiple.

So shouldn't PerCall be ensuring an instance is created for each call, as per the final sentence?

Am I using Sessions? My client creates an instance of a Proxy for each call, so I wouldn't expect session behaviour.

c# wcf wcf-binding nettcpbinding

share|improve this question

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

share|improve this question

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

share|improve this question

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges

asked Mar 27 at 14:50

OffHeGoesOffHeGoes

1,0491616 silver badges4040 bronze badges