[Openroad-users] eClient / App Server crashing

[Martin Pomej]

Hi Bodo,

Both values are set to 0. 


Regards, 
Martin Pomej

MyWorkplace Solutions Pty Limited
Level 5, 11 Queens Road
Melbourne Victoria 3004
 
Ph.   1300 733 731
Mob. 0414 230 845
Making Service our Priority
 
www.MyWorkplace.com.au
 
If you receive this email by mistake, please notify us and do not make any
use of the email. We do not waive any privilege, confidentiality or
copyright associated with it.

-----Original Message-----
From: Bodo.Bergmann at t-online.de [mailto:Bodo.Bergmann at t-online.de] 
Sent: Wednesday, 20 December 2006 18:39
To: martin.pomej at myworkplace.com.au; International OpenROAD Users
Subject: Re: [Openroad-users] eClient / App Server crashing

Martin,

what are the settings for the server app in VASA (registry), i.e.
regarding "Timeout" and "Transactions".
If not set to 0 (no limit), whenever such a limit is reached, the ASO would
be terminated, so the RestoreContext() would fail as the next call is routed
to a new ASO instance.
 
Bodo.

-----Original Message-----
Date: Wed, 20 Dec 2006 05:19:34 +0100
Subject: [Openroad-users] eClient / App Server crashing
From: "Martin Pomej" 
To: "'International OpenROAD Users'" 

    Hello  OpenROAD'ers,   OR 4.1 SP3 p11015  running App Server on Windows
2003 and eClients on XP SP2.   I'm  having a massive head ache at a
customer's site with eClient / App Server and I'm hoping that people out
there may have  experienced something similar.   Very frequently the
following error is occurring, by this I mean it'll re-occur in approx  10
minutes:
Fatal error: (-101) uc_context_mgr.RestoreContext: Cannot  restore session
context.
ContextId 40914 not found.

NB: the ContextId  changes each time we encounter the  error.   The only way
to resolve the problem is  for the user to restart their pc and the admin
guys to restart App Server. After  that's done the very same user will be
able to use the eClient application  without any error.    Our application
is  stateful and to me the above error gives the impression that the eClient
is  losing it's session with the server and hence falling over. But the
million  dollar question, what's causing the eClient to lose it's session,
if that is the problem?????    Our  client has approx 500 users using the
system all through the day, and  at any one point in time they could have
roughly 20 concurrent users.   The server machine has plenty of memory and
processing  power, and I have configured 4 name server entries and have left
VASA running, as per one of  Durwin's previous emails, so to achieve load
 balancing. Should there be only one name server or  can  anyone suggest any
setting(s) that may improve things?

I'm all out of ideas and the log  files are only showing the above session
context  error.

If it was a particular component I could reproduce the  problem and tackle
things that way, but that's not proving to be the  case.   Any help would
 be very much appreciated and may save a dent or two in what is already my
very  rough head.   Many thanks  and merry Christmas to all.   Regards,
_MARTIN  POMEJ_  

MyWorkplace  Solutions Pty Limited 

Level  5, 11  Queens Road 

Melbourne  Victoria 3004 

 

Ph.    1300 733 731 

Mob.  0414 230 845 

_Making  Service our Priority_ 

 

www.MyWorkplace.com.au [1] 

 

If  you receive this email by mistake, please notify us and do not make any
use of  the email. We do not waive any privilege, confidentiality or
copyright  associated with it.  

Links:
------
[1] http://www.myworkplace.com.au/