-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LogReceiverServer and SocketExceptions #378
Comments
Thanks I'll try to fix this soon |
Hi, can you show an example implementation LogReceiverService such as #381? |
Hi. I'm not to sure what you mean? Can I upload my demo apps to show the working of it? I simply start my host, the my client. Below is a listing of the output after just 4 LogEvent Transmissions: A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll |
Thanks, but I already wrote a demo application (in issue 381) using LogReceiverService. |
Ah, sorry, I understand now. I do not make use of the Wcf Service Host when testing. I've tried it now with your demo app, but nothing is output to the console so I cannot see if it also throws Sockect Exceptions, probably because it uses basicHttp? I'm using net.tcp for my binding. I'll give my thing a test with basicHttp and see if I get the same results as you |
I have noticed SocketExceptions and CommunicationExceptions are thrown on the Service's side when making use of LogReceiverService Target, after shutting down the client.
A SocketException is thrown for each 'transmission' that occurs. I have described it in more detail on StackOverflow here: http://stackoverflow.com/questions/23823350/nlog-to-wcf-closing-client-throws-socketexception-on-server
The text was updated successfully, but these errors were encountered: