D
dbeavon
Guest
In my case it was a session-managed client which had already set up an app-object/connection via the (1) connection event proc, and (2) it started a persistent procedure, and (3) it was waiting for the result of an "internal procedure" which was a very lengthy operation (lets say 2-3 minutes). In summary, the session was definitely not idle. It is hard to see in my screenshot, but the session was at "ACTIVE" and was assigned a SESSION ID of 4. It was running some ABL code that used to take under a minute (with a self-service connection to the database) but the duration had grown much longer now that we switched to using client-server connectivity to the database. Either way, I need PAS to allow the code to run to completion, and not categorize it as "idle", or try to kill it. Please let me know if there is anything more I need to do to convince PAS that the busy session is not idle. Before the 40 seconds expired, I saw an entry for this client in the "oe manager" screens under "sessions", "connections" and "agents". If it helps I can try to come up with a repro for tech support. Let me know if you'd like me to take that approach.
Continue reading...
Continue reading...