dotnet remoting: Expecting TcpChannel but finding TcpClientChannel -- dotnet remoting

Expecting TcpChannel but finding TcpClientChannel

Awanti
6/28/2006 10:31:00 PM

dotnet remoting: Hey everyone,

I have an application which registers the TcpChannel to call the remote
object.
The remoting configuration is in app.config

The code looks for existing TcpChannels and un-registers them before it
registers the channel customised with the security sinks.

Now..the problem I am facing is that when two instances of this
application are simultaneously started, in one of them when it goes
looking for existing TcpChannels, instead of finding an existing
TcpChannel it finds an existing TcpClientChannel and so the server
rejects the call ( as TcpClientChannel is not the custom channel but
TcpChannel is). I do not understand this !!!

Is there any such concept that when two processes do channel
manipulation at the same time, they interfere with each other ???

Any ideas??

-- Awanti

Re: Expecting TcpChannel but finding TcpClientChannel

Dave Sexton
7/4/2006 5:23:39 PM

Hi Awanti,

[quoted text, click to view]

How exactly are you doing this?

[quoted text, click to view]

The application is looking for channels that were registered by another
instance of your application?

[quoted text, click to view]

I doubt it.

[quoted text, click to view]