B
bartroose
Guest
Hi, We have been looking to facilitate diagnostics with AppServer as well (still on classic AppServer, OE 11.7). Couple of things we do: - Propagate client log settings from remote client to AppServer agent: In the Activate procedure on the agent, we apply client log settings of the requesting client (from context) and we set them back in the DeActivate procedure. Advantage is that you can selectively activate appserver client logging iff it comes from your remote client only. Same goes for other diagnostic settings like Profiler settings. Each request goes to a seperate prof.out file, but I can imagine you sometimes want otherwise. - From the remote client, run code which scans your appserver agent (SESSION:FIRST-BUFFER, FIRST-QUERY, FIRST-OBJECT) and send the data back in a dataset to the client. Run the same code on the local client and provide them in a UI, useful to detect memory leaks on client + appserver agent together (compare snapshots). BIND the appserver agent to your client by running a persistent proc on it. That way you - and only you- will land on that agent. After all, you appserver agent/session is an extension of your client session. You can also scan the TempTables of your appserver agnet and see what's inside. FYI Bart
Continue reading...
Continue reading...