Remoting Problem -- dotnet remoting

Stein Karlsen
9/2/2005 3:57:02 AM

Hi

I have 2 remoting servers where one is sending data to the other. One is
using tcpchannel and the other ipcchannel. The tcpchannel server is checking
a database for changes and when something in a specific table has changed it
sends that table to the other remoting server, that again passes the table to
a windows clients. It all works amazingly good but if nothing is happening
for about 5 minutes in my Windows clients, nothing happens. The next time I
do any changes in my database, the changes are not sent.

I have overridden the InitializeLifetimeService method in both my remote
classes returning nothing, so it should mean that my object should live
forever, right ?.
What else can cause this to happen ? Is there anywhere else I have to tell
that the connection between my two remoting system should never disconnect ?

regards

Stein Karlsen
9/2/2005 5:09:02 AM

Never mind
I found the solution.
I needed to override the InitializeLifetimeService in my event class also,
since that one also inherits rom MarshalByRefObjects

Stein

[quoted text, click to view]

Reema
9/21/2005 11:05:56 AM

Hi Stein,

I have the similar problem in my application, but my application do
some serialization and deserialization and after few moments of
inactivity my server throws serialization exception.

I tried to put breaks points in my application to check if the
connection was lost and i found out that after few minutes of
inactivity that is no action been done on client, my connection gets
removed from the connectionlist that is a hashtable that i maintain to
keep track of connections.

DO u know if this a .NET issue, or TCP channel issue. Why would the
connection break after a period of time?

Any help would be appreciated. Please do attach if you have any working
sample code.

Thanks,
Reema
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet remoting

dotnet remoting : Remoting Problem