D
dbeavon
Guest
By the time I know there is a problem, the MS-Agent is already long-gone, and I don't have any stacks (... but perhaps there is a configuration that would generate stacks while crashing?) I see this in the java (session-manager) logs : [xXUBwzg6RrejhqchK27x3g-agent-watchdog] WARN c.p.appserv.PoolMgt.AgentWatchdog - AgentWatchdog(xXUBwzg6RrejhqchK27x3g) : agent -927YaQeTdK7r2UAzbwm8A PID= 17580 has terminated. .. and Windows also reports the process crashing in the Application event log. But there is no good reason for that PID being killed (ie. no applicable agent/resource timeouts or anything). It typically happens because of a compiler or schema error while a single ABL session is running code. Typically this only affects us in development because that is where things are compiled on the fly and the schema is being actively changed. However, it is very disruptive, and *much* more difficult to troubleshoot than it should be (since there is absolutely *nothing* being reported to the agent log). I've found an earlier discussion that I tried to start about this here: PAS - Error generating asterix-asterix compiler message - Forum - OpenEdge Development - Progress Community According to that, it was a simple compiler error that causes _mproapsv to crash. It looks like so DS_Shift: WRITE-XML ( "FILE" , "shift.xml" , TRUE ) ...instead of... DATASET DS_Shift: WRITE-XML ( "FILE" , "shift.xml" , TRUE ) This is enough of a compiler problem to cause the whole MS-agent to die. And it doesn't put anything helpful in the agent log in the process of dying. The problems that cause ms-agent to die seem to be limited to a small set of compiler/schema issues. For example if I replace that line of code with something like this "asdfasdf", then things fail in a more expected way, with a compiler message to the agent log like so: ** Unable to understand after -- "asdfasdf". (247)). I am glad to know that this is a bug in PASOE. I will spend the time to open the tech support case next time I waste more than an hour trying to figure why my code caused the MS-agent to crash. Hopefully Progress has started their preparations for 11.7.4...
Continue reading...
Continue reading...