exactly how do you have you singleton object coded?
This is how I do mine. If you do it this way, then there isn't any way to register it
as a singleton object that I know of. The system will treat it just like any other
object, except it will not garbage collect it.
Private Shared mCurrentUser As CurrentUser
Public Shared Function Instance() As CurrentUser
If mCurrentUser Is Nothing Then
mCurrentUser = New CurrentUser()
GC.SuppressFinalize(mCurrentUser)
End If
Instance = mCurrentUser
End Function
-----Original Message-----
From: Manuel Costa [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 11:37 AM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] singleton server problem
Hi,
Is there a limit for the number of simultaneous calls to a remote object
registered as singleton?
I have an application with several servers and several clients per server.
After some amount of simultaneous calls to the servers they stop responding,
blocking any client call. When a client invokes a method it will stay
blocked and if i try to debug at the server side by putting a breakpoint in
the called method, nothing will happen. Is there any reasonable explanation
for this?
Manuel
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
