> I think multicast has some kind of connection to the multicast
> group. It make sense to me that no connection is a problem for that
> connection to the group. But I have no real experience.
Did some more investigations, the same problem was happening with a
normal UDP listening socket, as well as multicast. If it is still
listening when the network adaptor closes down, the socket seems to get
locked into a useless state.
Even closing the listening socket when the network connections is lost,
and re-opening it when the connection restarts does not resume real
listening.
I finally changed the component from static to dynamic so I could
destroy it when the connection was lost and re-create it later, and that
has solved the problem for broadcast and multicast.
Strangely, the same problem happened on one of the servers running the
same software in different mode, acting as a UDP proxy UDP forwarding
packets from one network to another, it stopped both listening and
sending at midnight when the two sockets were closed for 10 seconds and
then re-opened (so daily log files roll over cleanly), but never worked
again.
So perhaps there's a WSocket UDP close problem, something not being done
that happens when the component is freed and recreated.
I've not seen this problem with TCP, the same application listens on a
couple of TCP ports and those are opened OK before the network adaptor
is connected, and survive it being disconnected (probably!).
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
