![]() |
|
|
|
|
Change By:
|
Matthias Rump
(31/Jan/14 7:48 AM)
|
|
Environment:
|
Jenkins Version = 1.546
PTC Integrity Plugin Version =1.
20
22
Integration Point Server = Integrity Client Installation on the same server machine that runs Jenkins
Integrity Server / Client Version = 10.4
|
|
Description:
|
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.
Looking at the Integriy Server diag
It also shows that
,
we find and increasing
for each SCM Update Job started by jenkins, the
number of
sessions our CIUser's account
threads called "Client Instance Logger" increases by the "Checkout Thread Pool Size" defined in the plugin
.
So obviously there seem's to be a problem creating
These threads wait for ever
and
releasing API sessions by the plugin, which would IMHO explain the memory issue
never die
.
at ~300 waiting threads like these the client dies.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
