|
|
You're in the
dotnet remoting
group:Remoting Configuration Issue
dotnet remoting:
problem is this. This service has, until now, only provided services to client applications. Now, the service is going to be a client itself (it needs to remote to yet another service). I am trying to define two tcp channels: <channels> <!-- External clients use tcp on port 7777 --> <channel ref="tcp" port="7777" > <serverProviders> <formatter ref="binary" typeFilterLevel="Full" /> </serverProviders> </channel> <!-- Internal clients use http on port 7778 --> <channel ref="http" port="7778" > <serverProviders> <formatter ref="binary" typeFilterLevel="Full" /> </serverProviders> </channel> <!-- Support added for Centralized Cache --> <channel ref="tcp" port="9998"> <serverProviders> <formatter ref="binary" typeFilterLevel="Full" /> </serverProviders> </channel> </channels> When I do this in the config file, and try to start the service, it complains that the TCP channel is defined twice. It seems to me that since they are using separate ports, why should this make any difference? This third channel will be used for the service to connect to yet another service, but this time as a client. I think perhaps I am missing the whole point of these channels, and just don't have a good grasp of the whole process as remoting is new to me (this is a legacy app I am working on). Here is the exact error message I get: System.Runtime.Remoting.RemotingException: Remoting configuration failed with the exception System.Runtime.Remoting.RemotingException: The channel tcp is already registered. at System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel chnl) at System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel chnl) at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData) at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData). at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData) at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename) any help would be greatly appreciated. Please reply via newsgroup. Thank you very much for any assistance. Robert Reineri First National Bank of Marin
Robert,
The channel "tcp" is already registered. By not specifically naming tcp channels to unique names you are running into the error. Tcp channel has default name of "tcp". The return error has the user thinking a second Tcp channel can not be registered. See link for full explanation: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconchannels.asp - Marc [quoted text, click to view] "Robert Reineri" wrote:
> We have a service where we configure remoting via the configuration file. My > problem is this. This service has, until now, only provided services to > client applications. Now, the service is going to be a client itself (it > needs to remote to yet another service). I am trying to define two tcp > channels: > > <channels> > <!-- External clients use tcp on port 7777 --> > <channel ref="tcp" port="7777" > > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > > <!-- Internal clients use http on port 7778 --> > <channel ref="http" port="7778" > > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > > <!-- Support added for Centralized Cache --> > <channel ref="tcp" port="9998"> > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > </channels> > > When I do this in the config file, and try to start the service, it > complains that the TCP channel is defined twice. It seems to me that since > they are using separate ports, why should this make any difference? This > third channel will be used for the service to connect to yet another > service, but this time as a client. > > I think perhaps I am missing the whole point of these channels, and just > don't have a good grasp of the whole process as remoting is new to me (this > is a legacy app I am working on). > > Here is the exact error message I get: > System.Runtime.Remoting.RemotingException: Remoting configuration failed > with the exception System.Runtime.Remoting.RemotingException: The channel > tcp is already registered. > > at > System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel > chnl) > > at System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel > chnl) > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData > configData) > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > configData). > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > configData) > > at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename) > > any help would be greatly appreciated. Please reply via newsgroup. > > Thank you very much for any assistance. > > Robert Reineri > First National Bank of Marin > >
hi,
could you give more detail on this please? because I have the same problem and don't know how to solve it. What should I put in my <channel> line? mine is : <channel ref="tcp" port="8000"> </channel> thanks ThunderMusic [quoted text, click to view] "Marc" <Marc@discussions.microsoft.com> wrote in message news:BA3FB801-062D-4D0E-8530-B8BEAB869B1B@microsoft.com... > Robert, > > The channel "tcp" is already registered. By not specifically naming tcp > channels to unique names you are running into the error. Tcp channel has > default name of "tcp". The return error has the user thinking a second > Tcp > channel can not be registered. > > See link for full explanation: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconchannels.asp > > - Marc > > > "Robert Reineri" wrote: > >> We have a service where we configure remoting via the configuration file. >> My >> problem is this. This service has, until now, only provided services to >> client applications. Now, the service is going to be a client itself (it >> needs to remote to yet another service). I am trying to define two tcp >> channels: >> >> <channels> >> <!-- External clients use tcp on port 7777 --> >> <channel ref="tcp" port="7777" > >> <serverProviders> >> <formatter ref="binary" typeFilterLevel="Full" /> >> </serverProviders> >> </channel> >> >> <!-- Internal clients use http on port 7778 --> >> <channel ref="http" port="7778" > >> <serverProviders> >> <formatter ref="binary" typeFilterLevel="Full" /> >> </serverProviders> >> </channel> >> >> <!-- Support added for Centralized Cache --> >> <channel ref="tcp" port="9998"> >> <serverProviders> >> <formatter ref="binary" typeFilterLevel="Full" /> >> </serverProviders> >> </channel> >> </channels> >> >> When I do this in the config file, and try to start the service, it >> complains that the TCP channel is defined twice. It seems to me that >> since >> they are using separate ports, why should this make any difference? This >> third channel will be used for the service to connect to yet another >> service, but this time as a client. >> >> I think perhaps I am missing the whole point of these channels, and just >> don't have a good grasp of the whole process as remoting is new to me >> (this >> is a legacy app I am working on). >> >> Here is the exact error message I get: >> System.Runtime.Remoting.RemotingException: Remoting configuration failed >> with the exception System.Runtime.Remoting.RemotingException: The channel >> tcp is already registered. >> >> at >> System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel >> chnl) >> >> at >> System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel >> chnl) >> >> at >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData >> configData) >> >> at >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData >> configData). >> >> at >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData >> configData) >> >> at System.Runtime.Remoting.RemotingConfiguration.Configure(String >> filename) >> >> any help would be greatly appreciated. Please reply via newsgroup. >> >> Thank you very much for any assistance. >> >> Robert Reineri >> First National Bank of Marin >> >> >>
I don't know if attribute of name can be added to channel node to uniquely
identify channel in the config file. Chances are there is a way otherwise there would be a limit of 1 tcp or http server listener per app domain. For the code it would be as follows to name the channel: IDictionary prop = new Hashtable(); prop["name"] = "http1"; prop["port"] = "9001"; ChannelServices.RegisterChannel(new HttpChannel(prop, null, null)); - Marc [quoted text, click to view] "ThunderMusic" wrote:
> hi, > could you give more detail on this please? because I have the same problem > and don't know how to solve it. > What should I put in my <channel> line? > > mine is : <channel ref="tcp" port="8000"> </channel> > > thanks > > ThunderMusic > > "Marc" <Marc@discussions.microsoft.com> wrote in message > news:BA3FB801-062D-4D0E-8530-B8BEAB869B1B@microsoft.com... > > Robert, > > > > The channel "tcp" is already registered. By not specifically naming tcp > > channels to unique names you are running into the error. Tcp channel has > > default name of "tcp". The return error has the user thinking a second > > Tcp > > channel can not be registered. > > > > See link for full explanation: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconchannels.asp > > > > - Marc > > > > > > "Robert Reineri" wrote: > > > >> We have a service where we configure remoting via the configuration file. > >> My > >> problem is this. This service has, until now, only provided services to > >> client applications. Now, the service is going to be a client itself (it > >> needs to remote to yet another service). I am trying to define two tcp > >> channels: > >> > >> <channels> > >> <!-- External clients use tcp on port 7777 --> > >> <channel ref="tcp" port="7777" > > >> <serverProviders> > >> <formatter ref="binary" typeFilterLevel="Full" /> > >> </serverProviders> > >> </channel> > >> > >> <!-- Internal clients use http on port 7778 --> > >> <channel ref="http" port="7778" > > >> <serverProviders> > >> <formatter ref="binary" typeFilterLevel="Full" /> > >> </serverProviders> > >> </channel> > >> > >> <!-- Support added for Centralized Cache --> > >> <channel ref="tcp" port="9998"> > >> <serverProviders> > >> <formatter ref="binary" typeFilterLevel="Full" /> > >> </serverProviders> > >> </channel> > >> </channels> > >> > >> When I do this in the config file, and try to start the service, it > >> complains that the TCP channel is defined twice. It seems to me that > >> since > >> they are using separate ports, why should this make any difference? This > >> third channel will be used for the service to connect to yet another > >> service, but this time as a client. > >> > >> I think perhaps I am missing the whole point of these channels, and just > >> don't have a good grasp of the whole process as remoting is new to me > >> (this > >> is a legacy app I am working on). > >> > >> Here is the exact error message I get: > >> System.Runtime.Remoting.RemotingException: Remoting configuration failed > >> with the exception System.Runtime.Remoting.RemotingException: The channel > >> tcp is already registered. > >> > >> at > >> System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel > >> chnl) > >> > >> at > >> System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel > >> chnl) > >> > >> at > >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData > >> configData) > >> > >> at > >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > >> configData). > >> > >> at > >> System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > >> configData) > >> > >> at System.Runtime.Remoting.RemotingConfiguration.Configure(String > >> filename) > >> > >> any help would be greatly appreciated. Please reply via newsgroup. > >> > >> Thank you very much for any assistance. > >> > >> Robert Reineri > >> First National Bank of Marin > >> > >> > >> > >
Hi Robert,
Channels registered to the same application domain must be uniquely named within the domain. TcpChannel objects have the default name "tcp" , whereas HttpChannel objects take the default name "http". You need to change these default names if you want to register more than one TcpChannel or HttpChannel in a single doman. For example, you could give names to channel objects in your configuration file as follows: <channel ref="tcp" port="7777" name="ChannelA"> .... </channel> <channel ref="tcp" port="9998" name="ChannelB"> .... </channel> Hope this helps, Ramu Nallamothu [quoted text, click to view] "Robert Reineri" <SORRYSPAMMER@NOJUNK.COM> wrote in message news:uXYkUQQBGHA.3944@TK2MSFTNGP10.phx.gbl... > We have a service where we configure remoting via the configuration file. > My problem is this. This service has, until now, only provided services to > client applications. Now, the service is going to be a client itself (it > needs to remote to yet another service). I am trying to define two tcp > channels: > > <channels> > <!-- External clients use tcp on port 7777 --> > <channel ref="tcp" port="7777" > > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > > <!-- Internal clients use http on port 7778 --> > <channel ref="http" port="7778" > > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > > <!-- Support added for Centralized Cache --> > <channel ref="tcp" port="9998"> > <serverProviders> > <formatter ref="binary" typeFilterLevel="Full" /> > </serverProviders> > </channel> > </channels> > > When I do this in the config file, and try to start the service, it > complains that the TCP channel is defined twice. It seems to me that since > they are using separate ports, why should this make any difference? This > third channel will be used for the service to connect to yet another > service, but this time as a client. > > I think perhaps I am missing the whole point of these channels, and just > don't have a good grasp of the whole process as remoting is new to me > (this is a legacy app I am working on). > > Here is the exact error message I get: > System.Runtime.Remoting.RemotingException: Remoting configuration failed > with the exception System.Runtime.Remoting.RemotingException: The channel > tcp is already registered. > > at > System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel > chnl) > > at > System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel > chnl) > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData > configData) > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > configData). > > at > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > configData) > > at System.Runtime.Remoting.RemotingConfiguration.Configure(String > filename) > > any help would be greatly appreciated. Please reply via newsgroup. > > Thank you very much for any assistance. > > Robert Reineri > First National Bank of Marin >
Ramu,
I was having the same problem. This seems to have solved it. Thanks for your straight forward answer! - Porko [quoted text, click to view] "Ramu Nallamothu" wrote:
> Hi Robert, > > Channels registered to the same application domain must be uniquely named > within the domain. TcpChannel objects have the default name "tcp" , whereas > HttpChannel objects take the default name "http". You need to change these > default names if you want to register more than one TcpChannel or > HttpChannel in a single doman. > > For example, you could give names to channel objects in your configuration > file as follows: > > <channel ref="tcp" port="7777" name="ChannelA"> > > .... > </channel> > > > <channel ref="tcp" port="9998" name="ChannelB"> > > .... > </channel> > > > Hope this helps, > Ramu Nallamothu > > > > > > > > > > "Robert Reineri" <SORRYSPAMMER@NOJUNK.COM> wrote in message > news:uXYkUQQBGHA.3944@TK2MSFTNGP10.phx.gbl... > > We have a service where we configure remoting via the configuration file. > > My problem is this. This service has, until now, only provided services to > > client applications. Now, the service is going to be a client itself (it > > needs to remote to yet another service). I am trying to define two tcp > > channels: > > > > <channels> > > <!-- External clients use tcp on port 7777 --> > > <channel ref="tcp" port="7777" > > > <serverProviders> > > <formatter ref="binary" typeFilterLevel="Full" /> > > </serverProviders> > > </channel> > > > > <!-- Internal clients use http on port 7778 --> > > <channel ref="http" port="7778" > > > <serverProviders> > > <formatter ref="binary" typeFilterLevel="Full" /> > > </serverProviders> > > </channel> > > > > <!-- Support added for Centralized Cache --> > > <channel ref="tcp" port="9998"> > > <serverProviders> > > <formatter ref="binary" typeFilterLevel="Full" /> > > </serverProviders> > > </channel> > > </channels> > > > > When I do this in the config file, and try to start the service, it > > complains that the TCP channel is defined twice. It seems to me that since > > they are using separate ports, why should this make any difference? This > > third channel will be used for the service to connect to yet another > > service, but this time as a client. > > > > I think perhaps I am missing the whole point of these channels, and just > > don't have a good grasp of the whole process as remoting is new to me > > (this is a legacy app I am working on). > > > > Here is the exact error message I get: > > System.Runtime.Remoting.RemotingException: Remoting configuration failed > > with the exception System.Runtime.Remoting.RemotingException: The channel > > tcp is already registered. > > > > at > > System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel > > chnl) > > > > at > > System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel > > chnl) > > > > at > > System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData > > configData) > > > > at > > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > > configData). > > > > at > > System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData > > configData) > > > > at System.Runtime.Remoting.RemotingConfiguration.Configure(String > > filename) > > > > any help would be greatly appreciated. Please reply via newsgroup. > > > > Thank you very much for any assistance. > > > > Robert Reineri > > First National Bank of Marin > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |