huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix the build by passing allowConnectionDraining from SocketNodeInstance

This commit is contained in:
SteveSandersonMS 2017-01-20 18:09:57 +00:00
parent 6a1f35da8f
commit a9bc1201d1
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs
View File

@ -62,11 +62,15 @@ namespace Microsoft.AspNetCore.NodeServices.Sockets
{ {
if (_connectionHasFailed) if (_connectionHasFailed)
{ {
// _connectionHasFailed implies a protocol-level error. The old instance is no longer of any use.
var allowConnectionDraining = false;
// This special exception type forces NodeServicesImpl to restart the Node instance // This special exception type forces NodeServicesImpl to restart the Node instance
throw new NodeInvocationException( throw new NodeInvocationException(
"The SocketNodeInstance socket connection failed. See logs to identify the reason.", "The SocketNodeInstance socket connection failed. See logs to identify the reason.",
null, details: null,
nodeInstanceUnavailable: true); nodeInstanceUnavailable: true,
allowConnectionDraining: allowConnectionDraining);
} }
if (_virtualConnectionClient == null) if (_virtualConnectionClient == null)