D
dbeavon
Guest
There are many claims made in the docs that my legacy state-reset appservers are supposed to be able to be migrated to PAS. But I'm finding this a bit harder to do than I expected. Perhaps I missed something. While the QUIT statement in the disconnect procedure is clearing out the AVM session, its not re-running either of the startup procs (either session startup or agent startup). I would expect the session startup proc to be re-run. Ideally the whole session would be blown away but OEE continues to show the same session ID & start-time. I need my session startup proc executed or the "state-free" stuff won't work properly (we do a whole lot of "state-free" and a small amount of "state-reset"). Here is some QUIT documention: https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dvref/quit-statement.html In a PAS for OpenEdge application, you typically use this statement for a client connected using the session-managed application model, where you want to emulate the behavior of an AppServer running in the state-reset operating mode. In this case, you execute QUIT as the final statement in the PAS for OpenEdge Disconnect procedure after setting the SERVER-CONNECTION-BOUND-REQUEST attribute on the SESSION handle to FALSE. This cleans up the server session for access by the next client request that also emulates access to an AppServer in the state-reset operating mode. More links: documentation.progress.com/.../index.html documentation.progress.com/.../index.html
Continue reading...
Continue reading...