Feature #8900
memory management for FWD contexts
0%
History
#1 Updated by Constantin Asofiei 8 days ago
All FWD clients run in the same FWD server JVM. This includes Web/ChUI clients, batch processes and also appserver agents.
When deploying FWD 'at scale', the server can end up with 1000s of 'live' contexts - this can be especially seen with the proper PASOE support.
We need a way to measure the memory consumption for a FWD context. This will help in identifying 'runaway' FWD contexts (be it a batch process, agent or normal UI client), which for example has a memory leak not in the FWD code, but in the application code - this will allow automatic termination of these clients. For appserver requests, we may want to just terminate that agent only after it finished the request/gets unbound.
This monitoring tool can start measuring the FWD contexts memory usage once the garbage collection or the FWD server heap usage reaches a certain threshold.