This repository has been archived by the owner on Nov 12, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
WCF Timeout Exception #1
Comments
Update: This seems to occur using the following sequence: The server is running Two or more clients Subscribe. The server sends out a message. The clients all receive the message, just fine. One or more clients disconnect or unsubscribe. The server sends out a message. 1 minute later, the server crashes based on the "TimeoutException" |
I'm quite busy this weekend (turning 30 tomorrow) but I'll take a look at this in the beginning of next week. Thanks for reporting it! |
Catching timeout exception when trying to publish to a disconnected client and removes that client from the list. Closed by 1abcbd2 |
Works perfectly! Thanks! |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First, congrats on a great simple networking implementation.. it's very nice!
Now on to the gory stuff:
I set up three c# projects, one is a Windows Service, another is a simple Windows Forms project, and a third is a class library containing IEvent derived classes.
I am running the windows service, which will occasionally send out messages to the Windows forms client via Nvents. This works very well. I can have any number of instances of the Windows client running and they all recieve the messages from the service.
What goes wrong, is if any of the connected Windows Clients are disconnected, either with Events.Unsubscribe<> or losing the network connection, roughly a minute or so later, the Windows service will exit because of the WCF TimeoutException that is thrown.
So far, I haven't been able to find a workaround for this. Nor have I found a way to trap the TimeoutException. Any ideas?
The text was updated successfully, but these errors were encountered: