|
||||||||
|
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.
Hi Matthias,![]()
This is all great debugging... I hate to say this but you are barking up the wrong tree
While, I'm not in the least surprised that the number of threads directly contribute to the number of 'API Sessions' and hence 'Client Instance Logger' threads. The fact of the matter remains, this is exclusively an Integrity API problem.
The part where the plugin is responsible is to "terminate" the API Session after the thread is done. Which I have done and now there are no more lingering API Sessions (connections) to the server after the threads have completed.
Obviously, calling the terminate sequence is not killing the 'Client Instance Logger' threads which the API starts up on its own (and in its own JVM server or client). I've no way to control that. I'm doing my part as it relates to the "api contract"... now its up to R&D to fix their API issue.
Thanks!
Cletus