|
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!
Monitoring the client shows that the garbage collection is running, but seems to find nothing to delete.
Looking at the Integriy Server diag, we find and increasing number of sessions our CIUser's account.
So obviously there seem's to be a problem creating and releasing API sessions by the plugin, which would IMHO explain the memory issue.
|
