Remoting: singleton well-known

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using singleton well-known remoted object.

My client applictaion creates an instance of the object, and the remoting
plumbing works, creating the transparrent proxy and so on...

The server's method adds the received parameters to some collection, starts
some threads to do work on that data, and returns.

Now, if I my client app tries to call the same method on the remoted object,
the client app throws a "System.Threading.ThreadStateException" exception
with a message to the effect that the thread is terminated or running and
cannot restart.

If a separate client app tries to call the method, it's okay though.

Is this behavior by design? How can I get around it, to allow multiple
successive calls from the client to the server on a well-known singleton?
Or can I? Maybe I have to think about using client-activated remoting
instead?

Any guidance appreciated.

Thanks,
A
 
Sorry,

The problem was with another piece of code entirely. It had nothing to do
with the remoting. Please ignore.


-A
 
Back
Top