Classloading problem when using RTC Client libs
We developed 2 Jenkins plugin that uses RTC Plain Client 6.0.x libs.
Both plugins are called from within a Jenkins build, in a sequence, and the first one to be executed works, while the next fails with the following Exception:
When I restart the Jenkins instance (thus the JVM) and execute the plugins in the inverted order, still the first one succeeds, the second fails. Both plugins are using exactly the same snippet below to log into the server:
* LoginHandler implements ILoginHandler and ILoginInfo If Jenkins classloader is loading only one of the versions -- therefore both plugins have the same set of libs loaded -- how come the second one to execute always fails to find that package? This is an answer from Jenkins community. Jesse Glick is one of the main contributors of the Jenkins core. |
2 answers
Hi Rafael,
Didn't you have an RTC work item for this one? Looks familiar. Cheers --Rupa Comments
Rafael Rezende
commented Oct 19 '16, 12:08 p.m.
Hi Rupa!
Hi Rafael,
|
Hi Rafael, in previous MarshallingExceptions I have seen it's not because of a marshalling problem, rather because there is an UUID that conflicts. So it's going to be something deeper than marshalling.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.