|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
We are constructing a URL class loader with the plugin jar that contains BuildClient and all the toolkit jars. I am not sure how the class path can be involved with that. The BuildClient is in the same jar as RTCFacade that is trying to instantiate it.
How are you starting the slave? I want to confirm you aren't adding all the toolkit jars to its class path.
Only thing I can think of is if all the slaves are referencing the same set of jars that there could be contention there. Maybe they are being prevented from reading the jars to resolve classes?