Remoting Events fail if network not connected until after app starts
-
The scenario: Peer-to-peer network through a switch; no DNS, all fixed addresses. Main app establishes a remoting connection (Activator.GetObject) to a marshalled singleton object in a service on another machine. The app reads properties and invokes methods on the remote object. It also subscribes, through a wrapper, to events raised by the remote object. Remoting is configured in the config file on both ends. What works: All actions initiated by the app. Also, by monitoring the periodic events from the remote object, the app detects loss of connection (whether from physical disconnect or termination of the remote object) and will automatically recover when the object again becomes available. This has been extensively exercised. What fails: If the app's host machine is not physically connected to the switch until after the app starts, the event subscriptions fail to work. The app gets no notice of this. The remote object gets a "connection actively refused" exception when it invokes the event delegate. :wtf: Already tried: Delaying instantiation of the event wrapper until after the first time the remote host could be successfully pinged. No change. Please note: EVERYTHING works great as long as the network cable was connected at the time the app was started. All events are properly delivered and all subsequent disconnects are appropriately handled with successful recovery upon reconnect. The only known difference between the working and non-working scenarios is WHEN the network cable was connected to the switch: before or after the app starts. I'm at a loss for where to look next. :confused: What am I missing? (Also, should I cross-post this to the .NET Framework forum?)