{"action":"closed","issue":{"url":"https://api.github.com/repos/Azure/azure-iot-protocol-gateway/issues/61","repository_url":"https://api.github.com/repos/Azure/azure-iot-protocol-gateway","labels_url":"https://api.github.com/repos/Azure/azure-iot-protocol-gateway/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/Azure/azure-iot-protocol-gateway/issues/61/comments","events_url":"https://api.github.com/repos/Azure/azure-iot-protocol-gateway/issues/61/events","html_url":"https://github.com/Azure/azure-iot-protocol-gateway/issues/61","id":170241735,"number":61,"title":"Protocol gateway throwing Socket errors and TLS handshake failures subsequently even before a Device Connect.","user":{"login":"whizlingo","id":13106609,"avatar_url":"https://avatars.githubusercontent.com/u/13106609?v=3","gravatar_id":"","url":"https://api.github.com/users/whizlingo","html_url":"https://github.com/whizlingo","followers_url":"https://api.github.com/users/whizlingo/followers","following_url":"https://api.github.com/users/whizlingo/following{/other_user}","gists_url":"https://api.github.com/users/whizlingo/gists{/gist_id}","starred_url":"https://api.github.com/users/whizlingo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whizlingo/subscriptions","organizations_url":"https://api.github.com/users/whizlingo/orgs","repos_url":"https://api.github.com/users/whizlingo/repos","events_url":"https://api.github.com/users/whizlingo/events{/privacy}","received_events_url":"https://api.github.com/users/whizlingo/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-08-09T18:48:24Z","updated_at":"2016-08-12T21:38:18Z","closed_at":"2016-08-12T21:38:18Z","body":"While running the Protocol gateway in the simultar on TLS , we have noticed that as soon as the channel is active, the ExceptionCaught method gets called having exception set to {\"An existing connection was forcibly closed by the remote host\"} with exception trace stack trace pointing at below :\r\n\r\n`at DotNetty.Transport.Channels.Sockets.SocketChannelAsyncOperation.Validate()\r\n   at DotNetty.Transport.Channels.Sockets.AbstractSocketByteChannel.SocketByteChannelUnsafe.FinishRead(SocketChannelAsyncOperation operation) `\r\n  \r\n   \r\n  The **ExceptionCaught** implementation then calls the **ShutDownOnError** in Protocol gateway which in turns calls the self shutdown (The current state flag value is \"Waiting for connect\"). This continues to happen in cycle and keeps logging tons of errors in the logs along with TLS handshake warning due to the \"**UserEventTriggered**\" getting triggered with failed status.\r\n  \r\nThis all happens even before device could connect. In a normal device connect session ,this does not happen in this fashion as it quickly moves the state to processing connect and then connected.\r\n  \r\n  We are currently running a version of Protocol gateway dated (2nd of June) which does not have the latest bits also pointing to its respective dotnetty.  \r\n\r\n\r\n"}}
{"actor":{"display_login":"nayato"}}