In high load scenarios where massive amounts of job life cycle notifications are generated, I observed the following issues:

• on the server side, the notifications tend to accumulate in queues associated with the client connections, leading to large increases in heap usage, even OOMEs if the JPPF driver's heap is not large enough. This is not a memory leak, but rather a large spike in heap usage.
• on the client side (e.g. the admin console configured with immediate notifications mode), the notification handling will use a separate thread for each notification, leading to threads proliferation (I observed cases with a peak of over 30,000 live threads), leading in turn to the process being completely frozen