Skip to content
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

Closed
pjdupreez opened this issue Jun 25, 2014 · 5 comments
Closed

LogReceiverServer and SocketExceptions #378

pjdupreez opened this issue Jun 25, 2014 · 5 comments
Labels
bug Bug report / Bug fix
Milestone

Comments

@pjdupreez
Copy link

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

@ghost
Copy link

ghost commented Jul 1, 2014

Thanks I'll try to fix this soon

@AVKib
Copy link

AVKib commented Jul 4, 2014

Hi, can you show an example implementation LogReceiverService such as #381?

@pjdupreez
Copy link
Author

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.
I transmit some LogEvents from the Client to the Host using LogReceiverServer.
I close the client first, and then noticed a whole bunch of Exceptions in the Debug Output (one for each LogEvent Transmission)

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
A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll
A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll
A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll
A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll
A first chance exception of type 'System.ServiceModel.CommunicationException' occurred in System.ServiceModel.Internals.dll
A first chance exception of type 'System.ServiceModel.CommunicationObjectAbortedException' occurred in System.ServiceModel.dll

@AVKib
Copy link

AVKib commented Jul 8, 2014

Thanks, but I already wrote a demo application (in issue 381) using LogReceiverService.

@pjdupreez
Copy link
Author

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

@ghost ghost mentioned this issue Aug 4, 2014
@ghost ghost closed this as completed in 138fd2e Aug 6, 2014
@ghost ghost added the bug label Aug 6, 2014
@ghost ghost added this to the 3.1.1 milestone Aug 6, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report / Bug fix
Projects
None yet
Development

No branches or pull requests

2 participants