Using the PTC Integrity Plugin leads to a Out of Memory exceptions- and effectively kills the underlying Integrity Client that serves as "Integration Point Server" (within hours).

As recommended by the PTC support team, we do not use our Integrity Server directly but let a locally installed Integrity Client serve as "Integration Point Server".
This used to work fine for earlier versions, where a known bug in the Integrity API Implementation might lead to memory issues. Utilizing the server directly had even killed our Integrity server several times and in our current setup, at least only the "Integration Point Server" aka local client dies.

It still worked with Plugin 1.18
---------------------------------------------------------------------------
Since Plugin Version 1.20, the local Integrity Client's memory usage grows with every polling and every workspace update job performed!

This improved with version 1.22, as the memory consumption is now growing slower.

But still the Client won't last 8 hour.
---------------------------------------------------------------------------

Monitoring the client with "Java Visual VM" shows that the garbage collection is running, but seems to find nothing to delete.

It also shows that, for each SCM Update Job started by jenkins, the number of threads called "Client Instance Logger" increases by the "Checkout Thread Pool Size" defined in the plugin.

These threads wait for ever and never die.

at ~300 waiting threads like these the client dies.