Please, provide logs. Stacktrace is expected behaviour because some things in Jenkins works asynchronously and jenkins prints stacktraces even for expected behaviours.
On Sunday, September 6, 2015 at 10:20:37 PM UTC+3, Stanislav Baiduzhyi wrote: > > 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/3acdbc28-60d6-4b1d-bd4c-ccccf3472ff8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
