D
dbeavon
Guest
I've had this happen on a number occasions. Our databases are restarted every weekend. And this obviously impacts all directly connected database clients. But the PASOE instance is running on a different server with client/server connections. I would expect that PASOE would fail to process the first set of requests that arrive the next day, but would eventually recover and start up *new* MS-agents and/or new sessions within existing agents that would be properly connected to the database. However what I'm finding is that PASOE does not recover on its own from these situations and I'm required to go stop the ms-agents manually via OEE. After the ms-agents are stopped, things start working again. The client typically detects STOP conditions and they don't go away, no matter how many retries are attempted: [09:29:45.244] CONNECTING to: serv001:8810/.../apsv ... [09:29:45.249] RUN: persistent procedure - app/Production/AppServer/Shift.p [09:29:45.252] RUN: internal procedure - GetShiftData Exception thrown: 'Progress.Open4GL.DynamicAPI.FGLErrorException' in Progress.o4glrt.dll Exception thrown: 'Progress.Open4GL.Exceptions.RunTime4GLStopException' in Progress.o4glrt.dll Exception thrown: 'Progress.Open4GL.Exceptions.RunTime4GLStopException' in Progress.o4glrt.dll Exception thrown: 'Progress.Open4GL.Exceptions.RunTime4GLStopException' in Progress.o4glrt.dll Exception thrown: 'Progress.Open4GL.Exceptions.RunTime4GLStopException' in UFP.LumberTrack.AppServer.dll The failures in the PASOE logs (agent) look like so: [18/01/03@09:27:13.599-0500] P-005432 T-005464 1 AS-4 -- (Procedure: 'GetShiftData app/Production/AppServer/Shift.p' Line:192) Disconnect from server; database is being shutdown. (2659) [18/01/03@09:29:45.273-0500] P-005432 T-005464 1 AS-4 -- (Procedure: 'GetShiftData app/Production/AppServer/Shift.p' Line:192) app.Production.Shift Database lumbertrack not connected. (1006) The database not connected error will repeat indefinitely. I'm hoping someone else knows how to configure PASOE to recover from this situation. I'm betting that if I had a "resource timeout" in place then perhaps I wouldn't be affected as frequently because the chances would be higher that the ms-agent process would be automatically trimmed out of memory during the late hours when the database is restarted. However, even that isn't a guarantee. Ideally PASOE would have some special understanding of this type of problem (database not connected) and kill off the affected ms-agents so that he PASOE instance would recover on its own. Any tips would be appreciated. I guess the next step will be to start writing scripts to stop all PASOE sessions/agents whenever any database is restarted. I was hoping to hold off on this type of approach as long as possible...
Continue reading...
Continue reading...