-
Notifications
You must be signed in to change notification settings - Fork 48
Getting System.NullReferenceException #45
Comments
@rahulrajatsingh Could you tells us a little information?
From the stack trace, it looks like the exception is coming up when processing the response message generated by the service... it's not finding the same |
OK, found one possible repro scenario: This same exception will happen if the service operation that was called explicitly or implicitly ends up calling another remote service. However, it will only happen if the calling code instantiates a new var channel = new SomeServiceClient();
// the following line should be in a using statement
var scope = new OperationContextScope((IContextChannel)channel);
// use OperationContext for something
OperationContext.Current.OutgoingMessageHeaders.Add(new SomeCustomHeader());
// call service
channel.CallSomeOperation(); Code like this causes the OperationContext for the child call to be stuck on the current thread, so when we look at OperationContext.Current later on, we're getting the wrong context. |
Please find all the requested details below:
4.5.1
No
Yes we are pushing claims in the OutgoingMessageHeaders for other service calls.
No custom behavior. Its configured to use Single instance with Concurrency mode as Multiple and some throttling using configurations. |
@rahulrajatsingh Can you confirm if your code suffers by any chance of the issue mentioned above of not disposing correctly the Also, version |
I just added this package to my service and tested it. I am getting following exception just by adding this package dependency.
The text was updated successfully, but these errors were encountered: