Currently, the JPPF server (or driver) uses a soft references cache to store classes loaded from the connected clients, to make class loading requests from the nodes faster.

This can cause class loading issues in some scpecific scenarios, where the client dynamically loads new versions of the client classes. In this type of situation, since the client uuid does not change, the nodes will not request the new version of these classes if they have already loaded them.

There is a feature in the nodes, to reset the class loader associated with a client, however it only works with classes loaded from the classpath specified in this node class loader. Unfortunately, for classes loaded from the client, the reset is circumvented by the server cache.

Thus, we propose to implement the possibility to disable the server cache such that this reset can take place for classes loaded both locally and remotely by the nodes.