Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-26947] forcibly terminate Maven remoting channel when upstream channel get closed #39

Merged
merged 1 commit into from Aug 20, 2015

Conversation

ydubreuil
Copy link
Contributor

JENKINS-26947

Currently, when the main remoting channel is abruptly closed, Maven channel can be stuck for a while because it doesn't get notified of the disconnection.

@reviewbybees

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@ydubreuil
Copy link
Contributor Author

Some test are failing on CI. Had the same failure on my laptop on the master branch

@ndeloof
Copy link
Contributor

ndeloof commented Mar 24, 2015

@kohsuke would it maybe make sense to get this included in remoting ? Not sure channel-in-channel is a common pattern

@jglick jglick changed the title [FIX JENKINS-26947] forcibly terminate Maven remoting channel when upstream channel get closed [JENKINS-26947] forcibly terminate Maven remoting channel when upstream channel get closed Mar 24, 2015
@jglick
Copy link
Member

jglick commented Mar 24, 2015

Not sure channel-in-channel is a common pattern

No, only maven-plugin is this crazy (except for whatever code was copied & pasted into ivy-plugin).

I guess I am +0. If it fixes the problem then we need it. The patch is somewhat scary.

}

/**
* copy/paste of Channels.forProcess
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is a particular reason the existing method cannot be reused, it should be explained here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Channel.terminate() has protected visibility so LinkedChannelCleaner.onClose() can't call it directly

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you tried to move this hack-ish class to same hudson.remoting package so you can access it's protected method ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hudson.remoting package is in a signed jar file, so you will be SOoL if you try that

@ghost
Copy link

ghost commented Jul 1, 2015

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be
reviewed by other CloudBees employees before we seek to have the change accepted. If you want to find out
more about our process please see this note

@stephenc
Copy link
Member

stephenc commented Jul 6, 2015

🐝

@ydubreuil
Copy link
Contributor Author

@reviewbybees done

@ghost
Copy link

ghost commented Jul 8, 2015

This pull request has completed our internal processes and we now respectfully request the maintainers of this repository to consider our proposal contained within this pull request for merging.

@ydubreuil
Copy link
Contributor Author

@jglick Would you consider merging this PR? I can rebase to master and rerun test. I know it's pretty invasive but it's tested in real condition for some time now (there's a very big CloudBees DEV@cloud customer running fine with this patch)

@jglick
Copy link
Member

jglick commented Aug 11, 2015

It has a bee but it needs a merge.

@ndeloof
Copy link
Contributor

ndeloof commented Aug 12, 2015

@ydubreuil please rebase then we can merge

@jglick
Copy link
Member

jglick commented Aug 12, 2015

Rebase or just git merge master.

…stream channel get closed

Currently, when the main remoting channel is abruptly closed, Maven channel can be stuck for a while because it doesn't get notified of the disconnection
@ydubreuil
Copy link
Contributor Author

I've just rebased to master.

ndeloof added a commit that referenced this pull request Aug 20, 2015
[JENKINS-26947] forcibly terminate Maven remoting channel when upstream channel get closed
@ndeloof ndeloof merged commit 7171b20 into jenkinsci:master Aug 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants