fair enough. Can you break down your app to the relavent remoting
parts and post some code? I'll see if I can spot any problem areas.
On Wed, 3 Dec 2003 14:01:12 +0200, "adi vaturi" <2@a.com> wrote:
>Thanks for the response.
>
>I am sure the client finished treating the event. I added debug messages to
>the middleware and i it proved the middleware passes the event and returns.
>The client is not stuck, the server just not continue to run. By the way -
>at this point there is no way to communicate with the server's singleton
>object that suppose to live forever (from another client). And there is no
>way to stop or pause the debugger. You need to kill the server from the task
>manager.
>
>"Allen Anderson" <allen@sparkysystems.com> wrote in message
>news:9hfpsv4sfummo2t64rbe76tmp2qqc72k4q@4ax.com...
>> after handling the event in the client, are you certain that it is
>> returning? If a program hangs in the client then it will exhibit the
>> behavior you have mentioned.
>>
>>
>> Allen Anderson
>>
http://www.glacialcomponents.com >> mailto: allen@put my website url here.com
>>
>>
>>
>> On Thu, 27 Nov 2003 18:28:42 +0200, "adi vaturi" <adisi@nice.com>
>> wrote:
>>
>> >I have a client activated object that sends event to a client. Once in a
>> >while, the server or client got stuck. After investigating this, i found
>out
>> >that it all starts after the server sends an event to the client, the
>client
>> >finish treating it, but from some reason the server does not continue. As
>if
>> >the delegate didn't return.
>> >
>> >When calling other methods of this CAO will not reach the server and the
>> >client get stuck because of this.
>> >
>> >The server's and middleware InitializeLifeTimeService returns null, so
>the
>> >problem is not there. It also cannot be the client fault, since it
>finishes
>> >treating the event and continue to run.
>> >
>> >Any comments of further explanation would really be appreciated...
>> >
>> >Thanks,
>> >Adi. Vaturi.
>> >
>>
>
