Serviio consistently disconnects after about 2 hours

I have a Samsung PN51D7000 TV, a Linksys E4200 router and I'm currently running Serviio PRO v1.3.1 (Evaluation license) on a Dell XPS15 Windows 7 Home Premium 64-bit.

When I stream movies from http://www.einthusan.com it plays without any issues for a little over 2 hours and then consistently disconnects with the following error message in the logs: DEBUG [WebServer] I/O error: Software caused connection abort: socket write error

I see that this error seems to be occurring in between a bunch of SSDP messages, I don't know if they are related. I have included a chunk of the log below.

====================================================================================================================================
2013-08-27 20:45:43,680 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Samsung TV / player (C/D/E/F-series)'
2013-08-27 20:45:43,795 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.9:1025s
2013-08-27 20:45:43,795 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.9:1025
2013-08-27 20:45:43,834 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-ce-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1026s
2013-08-27 20:45:43,834 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1027s
2013-08-27 20:45:44,051 DEBUG [WebServer] I/O error: Software caused connection abort: socket write error
2013-08-27 20:45:44,231 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 85563072-d235-8e09-507b-92705a6925df from address /192.168.1.9:1028
2013-08-27 20:45:44,232 DEBUG [RendererManager] Adding renderer Renderer [uuid=85563072-d235-8e09-507b-92705a6925df, ipAddress=192.168.1.9, name=PN51D7000, profileId=7, manuallyAdded=false, forcedProfile=false, enabled=true, accessGroupId=1] to list of active renderers
2013-08-27 20:45:44,479 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 85563072-d235-8e09-507b-92705a6925df from address /192.168.1.9:1028
2013-08-27 20:45:49,186 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.9:1025s
2013-08-27 20:45:49,187 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.9:1025
2013-08-27 20:45:49,191 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-ce-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1026s
2013-08-27 20:45:49,230 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1027s
2013-08-27 20:45:49,292 DEBUG [SearchManager] Committing search index
2013-08-27 20:45:49,489 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.9:1025s
2013-08-27 20:45:49,490 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.9:1025
2013-08-27 20:45:49,510 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-ce-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1026s
2013-08-27 20:45:49,511 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1027s
2013-08-27 20:45:49,790 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.9:1025s
2013-08-27 20:45:49,791 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.9:1025
2013-08-27 20:45:49,797 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-ce-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1026s
2013-08-27 20:45:49,800 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:RemoteUIServerDevice:1 from address /192.168.1.9:1027s
2013-08-27 20:45:51,232 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 85563072-d235-8e09-507b-92705a6925df from address /192.168.1.9:1028
2013-08-27 20:45:51,503 DEBUG [DiscoverySSDPMessageListener] Received a valid NOTIFY (ssdp:alive) message from Renderer 85563072-d235-8e09-507b-92705a6925df from address /192.168.1.9:1028
====================================================================================================================================

I have "Filter Multicasting" selected on my Linksys E4200 router.

If the movies are shorter that 2 hours, it does play normally and even starts the next movie. But I have never tried watching a 2nd one. So I don't know if that would disconnect when it hits the 2 hour mark ( a little over 2 hours; like 2 hours and 10 minutes ).

Please help. Thanks,
Serviio_snc

[zip]

This means the device closed the connection. For what reason I'm not sure, but it might be the SSDP messages being received. Not sure how the TV handles them. Or if the network is causing this.

So, does it look like my TV is closing the connection?

From the log, does it looks like the SSDP messages are coming from the TV [192.168.1.9 is the TV] ?

Is there anything I should try to stop these messages? in my router setting or in the firewall on the PC running serviio?

[zip]

the SSDP messages are the way devices get discovered in UPnP. Around the disconnect, the TV requests serviio's description and makes some searches for additional services, then disconnects, then the TV sends notification that it's alive.

So either the TV somehow restarted the UPnP module, or didn't get serviio's response to the searches / description.

You could check some settings on your router related to multicast / IGMP