[Openroad-users] eClient / App Server crashing

[Durwin Wright]

Hello Martin,

 

It sounds like the ASO that is holding the context was restarted.  There
are a number of reasons why this would happen.  The best approach is to
turn on the SPO Log and wait until it happens again.  There will be
information logged that should be meaningful.  The SPO Log probably
should be running all of the time.   I have found it to be very useful
in the past.

 

If you have an issue opened, I would be very glad to monitor it and
assist if needed.  I have put together some documentation on how to read
and interpret the SPO Log.  It is part of the OpenROAD 2006 Server
Reference Guide.  

 

Durwin Wright | Sr. Architect | Durwin.Wright at ingres.com
<mailto:Durwin.Wright at ingres.com>  | Ingres | 500 Arguello Street |
Suite 200 | Redwood City | CA | 94063 | USA
<http://maps.google.com/maps?q=500+arguello+street,+94063&ll=37.487297,-
122.233200&spn=0.004602,0.012771&t=k&hl=en>   +1 650-587-5523 | fax: +1
650-587-5550 

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Martin Pomej
Sent: Tuesday, December 19, 2006 8:20 PM
To: 'International OpenROAD Users'
Subject: [Openroad-users] eClient / App Server crashing

 

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 <http://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.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20061220/971e4d1b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1433 bytes
Desc: image001.jpg
Url : http://peerlessit.com/pipermail/openroad-users/attachments/20061220/971e4d1b/attachment.jpe