ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Evo Auto Restarts Leaving Pervasive Ghost Sessions
http://www.istechforum.com/YaBB.pl?num=1636579834

Message started by gtladmin on 11/10/21 at 14:30:34

Title: Evo Auto Restarts Leaving Pervasive Ghost Sessions
Post by gtladmin on 11/10/21 at 14:30:34

I am seeing an unintended consequence of the automatic Evo restarts when the program count reaches a certain point (default of 20).

While it is reducing the number of reports of application and tack errors , it is leaving behind a wake of empty Pervasive Microkernel and SQL (Java) sessions for each user who gets a restart, and we can e see these "ghost" sessions in the Pervasive Monitor (that's what we call an empty session--no open files or locks being used).

The number of ghost sessions varies (but the # will be the same for Microkernel and SQL, so a user can have 14 of each) and I am not sure if it is based on the the program count or what is actually opened on the Evo desktop when the restart occurs. We have to manually clear these ghost sessions.

Just thought someone should know. I have been tracking this and these sessions definitely seem to coincide with the automatic restart when a program count is reached.

Kind regards,

Val

Title: Re: Evo Auto Restarts Leaving Pervasive Ghost Sess
Post by Lynn_Pantic on 11/10/21 at 18:54:42

"We have to manually clear these ghost sessions" - are they using any resources? Why do you have to clear them? I know you are one of the few installations using a Linux server so your observations may be different from others using Windows servers.

Title: Re: Evo Auto Restarts Leaving Pervasive Ghost Sess
Post by gtladmin on 11/11/21 at 13:18:26

Because we have learned to monitor connections in Pervasive monitor. We have some staff that have a habit of doing things that either kick them out of Evo (application errors they ignore) or they CTRL-ALT-DEL out of Evo when they've locked it up through impatience. So those sessions get left behind, and we clear them out. We also can see which sessions are locking a file when someone gets a continuous Pervasive code that the file is locked by someone else. Usually someone is mid-way through a process and just either levaes their desk, stops to talk, or takes a phone call and just leaves Evo waiting for a response. Or, at the end of the day we hav everyone out of Evo for posting (learned this is something we need to do), and we can make sure no one hops in to disturb the processing, or when we run MRP we have learned to run it with none of the MRP talbes open by anyone else.

We also look at the SQL sessions to moinitor connections for UPS and FedEx, and java things that may get hung up like sometimes Features and Options (it's user related).

So we just keep Pervasive monitor open. ::)