Remoting loses subscription but not proxy
-
The scenario: 1. Windows service, running on 2 machines; each marshals a singleton remoting object. 2. Events are passed thru an intermediary per recommendations in articles on Remoting Events. 3. Client, running on one of the 2 machines, connects to both services via remoting (TCP) and receives events from both. 4. Then... the LAN is physically disconnected from the client machine. 5. Loss of connection to the "other" machine is correctly noted and handled. Reconnection of the LAN cable results in correct recovery of that remoting connection. No problem there. 6. Problem: The next event delivery from the "local" service fails with "The connection was forcibly closed..." (Why, pray tell?) and the event delegate is appropriately removed (it's an expected result when the client "leaves"). The remoting proxy to the local service remains intact, so the client never knows that its event subscription has been lost and it never gets restored. X| 7. Oddity: If the LAN cable is unplugged before the client attempts the remoting connections, the resulting subscription to the local server events is unaffected by subsequent LAN connections and disconnections! :~ Obviously, something about the remoting path is different. Q1: Can I force the insulated connection that occurs in (7) to happen even when the LAN is present? Q2: Failing Q1, can I detect or prevent the loss of the event connection that occurs in (6)? (C# explanations preferred)
-
The scenario: 1. Windows service, running on 2 machines; each marshals a singleton remoting object. 2. Events are passed thru an intermediary per recommendations in articles on Remoting Events. 3. Client, running on one of the 2 machines, connects to both services via remoting (TCP) and receives events from both. 4. Then... the LAN is physically disconnected from the client machine. 5. Loss of connection to the "other" machine is correctly noted and handled. Reconnection of the LAN cable results in correct recovery of that remoting connection. No problem there. 6. Problem: The next event delivery from the "local" service fails with "The connection was forcibly closed..." (Why, pray tell?) and the event delegate is appropriately removed (it's an expected result when the client "leaves"). The remoting proxy to the local service remains intact, so the client never knows that its event subscription has been lost and it never gets restored. X| 7. Oddity: If the LAN cable is unplugged before the client attempts the remoting connections, the resulting subscription to the local server events is unaffected by subsequent LAN connections and disconnections! :~ Obviously, something about the remoting path is different. Q1: Can I force the insulated connection that occurs in (7) to happen even when the LAN is present? Q2: Failing Q1, can I detect or prevent the loss of the event connection that occurs in (6)? (C# explanations preferred)
RESOLVED: The solution is to use IPC on the local machine for both directions--the proxy and the callbacks. When doing so, though, the IPC channel for callbacks has to be hidden from the marshaling on remote machines. See http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dotnet.framework.remoting&mid=f5d1bb8b-2fa8-4347-82f0-12957a8f9776[^] for more detail.