D
dbeavon
Guest
What would be the goal for restarting an ABL application? We use lots of distinct ABL applications within a single instance. There is rarely a scenario where one of them needs to be managed independently of the others. Most of our management is done by trimming ABL sessions (ie. within an application). Or forcing the expiration of HTTP sessions. Or restarting individual msagent processes (mproapsv). Or restarting the entire instance. There is a lot of configuration related to an ABL application, but changes to that will take effect dynamically. Are you trying to restart to make a config change? Another thing I've noticed is that PASOE is fairly resilient. If you want to just terminate one of the mproapsv processes, you can do that at the OS level. I've found that you can basically just kill it out of task manager and PASOE will start up another one to take its place as needed. Of course this is a "quick-and-dirty" approach and Progress certainly wouldn't recommend it. In production our preferred approach to do maintenance is by using load-balancing and the "gracefully" removing a server from the load. Then after the server is inactive for a while, you can do any maintenance that is needed.
Continue reading...
Continue reading...