S
ssouthwe
Guest
In WebSpeed, sometimes you would have an agent get "stuck" and you could see that it was just burning resources and not completing the request. When a user gets impatient, they sometimes repeat the same request and get all your agents stuck. In the past, we'd see a given PID that had gone sideways, and need to figure out what it was running and who was running it. If the application code can figure out its PID (and in this case, it's thread) then it can be made to store that info along with other details about the request as a way of troubleshooting. So when something freezes in PID 999, you scan the records and see what the last thing was that started to run on that PID, and who the user was. Another thing we would do is have inter-process communication between WebSpeed agents for various things like having them refresh cached data after an update. With PIDs and ThreadIDs, we could track which agents have picked up the communication and performed the requested action. My hope is to have all the same abilities that we relied on in WebSpeed available in PASOE for these odd use cases.
Continue reading...
Continue reading...