Where do you see these traces? "slave.waitUntilOffline();" ensures that channel is null before existing, but I suppose that there could be exceptions from background monitoring threads and hanging jobs (good ones should be gracefully aborted).
воскресенье, 6 сентября 2015 г., 22:20:37 UTC+3 пользователь Stanislav Baiduzhyi написал: > > Hi All, > > Another question regarding custom cloud plugins: > > I'm creating a custom plugin that creates a node from prototype, uses > the node, discards it (or reverts the state). > > I'm starting slave.jar with tcp and connecting to it. My > ComputerLauncher also implements ExecutorListener, and disconnects on > taskCompleted, and terminates/discards the node in afterDisconnect. > But I see huge stack traces about socket being closed. > > I've copied the closing procedure from here: > > https://github.com/jenkinsci/vsphere-cloud-plugin/blob/master/src/main/java/org/jenkinsci/plugins/vSphereCloudSlave.java#L305 > > > So, what is the correct way to disconnect the channel before node > termination? > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f8321764-dd13-42ab-9e9e-333476eb62d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
