D
dbeavon
Guest
This may be a bit of a vague question but it would help me determine if/when to contact Progress technical support in regards to the behavior of PASOE. Are there scenarios where a single ABL session should run into a problem which is severe enough to take down the entire MS-agent process? Is that ever an appropriate/acceptable behavior (esp. given that the MS-agent is potentially hosting a lot of unrelated sessions)? Note that I'm not loading any third-party libraries or using the .Net runtime or anything like that, I'm just using run-of-the-mill ABL database code. It seems that this comes up for me from time to time and the root cause usually seems to be an ABL compilation problem or a schema problem (either r-code CRC schema or client-server/"SERV" schema). This problem is typically encountered in the ABL code running in a *single* session of the agent. It seems a bit severe that such a problem in a single session should take down the entire process, potentially including other ABL sessions which are having no problems at all. Another simultaneous issue is the lack of logging when this happens. Perhaps it is because of some internal indirection mechanism that PASOE uses for logging errors to the agent logs. When the entire ms-agent is terminated so quickly, it is unlikely that any meaningful message will appear in the agent logs. While you can see in the java (session manager) logs that the ms-agent is dead, you don't get to see the ABL-related reason in the agent log file. In order to troubleshoot, I typically need to do a log of guesswork to figure out what code may have been running at the time, and then try to run the same code in a an isolated "_progres" process. That provides more clues about what went wrong.
Continue reading...
Continue reading...