[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-19 Thread dogf...@java.net (JIRA)














































dogfood
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Integrated in  jenkins_main_trunk #2154
 [FIXED JENKINS-7114] (Revision 3cfa3e55a1f57b6634576a0d6d7ac044714e1022)

 Result = SUCCESS
kohsuke : 3cfa3e55a1f57b6634576a0d6d7ac044714e1022
Files : 

	changelog.html
	pom.xml





























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-19 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
 pom.xml
http://jenkins-ci.org/commit/jenkins/3cfa3e55a1f57b6634576a0d6d7ac044714e1022
Log:
  [FIXED JENKINS-7114]

The actual change is in the remoting 1.20.


Compare: https://github.com/jenkinsci/jenkins/compare/75fc9308a9f2...3cfa3e55a1f5




























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-19 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-7114 as Fixed


aborting download of workspace files makes slave agent hang
















Change By:


SCM/JIRA link daemon
(20/Dec/12 2:07 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-19 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/hudson/remoting/Capability.java
 src/main/java/hudson/remoting/Channel.java
 src/main/java/hudson/remoting/Command.java
 src/main/java/hudson/remoting/MimicException.java
 src/main/java/hudson/remoting/ProxyOutputStream.java
 src/test/java/hudson/remoting/DeadRemoteOutputStreamTest.java
http://jenkins-ci.org/commit/remoting/d084f5095f11a8bcb80913266d664b9d1f17dc3b
Log:
  [FIXED JENKINS-7114] fixed the layer confusion in the remoting

When ProxyOutputStream sends write(byte[]) to the other end and the actual write fails, "NotifyDeadWriter" object comes back and reports back that the write has failed. Without this mechanism, the writer side will keep on going.

Because the RemoteOutputStream service is a lower layer service that cannot rely on custom classloading service (doing so would create cyclic dependencies), when we send back this exception, the object graph of the exception needs to be deserializable on the receiver side. This is not the case when the exception class is defined by the user (as is the case of winstone.ClientSocketException.)

This fix addresses this problem by turning an exception class into another class that emulates the output of the original exception.

To make this change interopeable with earlier versions, we need to introduce a new capability flag. If we send MimicException to the other side and the other side doesn't have this class definition, then it'll cause automatic fail.


Compare: https://github.com/jenkinsci/remoting/compare/2b1ec8ab1528...d084f5095f11




























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-11 Thread martin.sche...@gcsc.uni-frankfurt.de (JIRA)














































Martin Scherer
 updated  JENKINS-7114


aborting download of workspace files makes slave agent hang
















Change By:


Martin Scherer
(11/Dec/12 7:47 PM)




Attachment:


stack.txt



























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-11 Thread martin.sche...@gcsc.uni-frankfurt.de (JIRA)














































Martin Scherer
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















I can confirm this behaviour. My Log has grown to 12Gb due to the continuous thrown (and not properly handled) exception.
Thanks in advance for fixing this soon!



























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






[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-11-22 Thread truck...@gmail.com (JIRA)














































Jes Struck
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















we have just upgraded from jenkins 1.490 -> 1.491 and are still seing this issue 
we are on ubuntu 12.04 LTS on both master and slaves
and using the ssh slave connector.

is there any one that havesolved this. it stackes up in the log file quit fast. so the log file grows to 2-3 GB in a couple of hours



























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