[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2016-02-22 Thread losti...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Jackson commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
Still an issue in Jenkins ver. 1.641 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-12-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28155 
 
 
 
  Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-08-26 Thread dan_albu...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Albu commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
I have started to have the same issues with the same configuration. I am using the LTS version of Jenkins 1.609.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-23 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
I have no actual solution for this problem but after doing many different experiments we managed to configure our windows slaves with a scheduled task (Jenkins Slave.xml attached here) and so far they are quite stable. A prerequisite is to have the test user automatically login at OS boot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-23 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28155 
 
 
 
  Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vassilena Treneva 
 
 
 

Attachment:
 
 JenkinsSlave.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-23 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva edited a comment on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 Ihavenoactualsolutionforthisproblembutafterdoingmanydifferentexperimentswemanagedtoconfigureourwindowsslaves (winserver2012R2standart) withascheduledtask(JenkinsSlave.xmlattachedhere)andsofartheyarequitestable.Aprerequisiteistohavethetestuserautomatically login logged atOSboot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-21 Thread w.male...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Waldek M edited a comment on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 *UPDATE*:Itturnedoutmyissuewasrelatedtotherecentswitchtohttps(soprobablynotrelatedtothisone).AfterprovidingJavatrustStorewithRootCAandIntermediateCA-issueresolved. Samehere-althoughreasonmightbedifferent.SlavestartedonWIndows7,onanADaccount,asaservice.Dropsalmostimmediately.{noformat}java.io.IOException:Connectionaborted:org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave] atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:java.io.IOException:Connectionresetbypeer atsun.nio.ch.FileDispatcherImpl.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) atsun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) atsun.nio.ch.IOUtil.read(IOUtil.java:197) atsun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) atorg.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) atorg.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ...6more{noformat}Foundsomemoreinslave'slog.MymasterinstanceisusinghttpsandalthoughthecertificateisinstalledinWindowsandbrowsersrecognizeit,slavecomplainsaboutit-asbelow.Anyideaswouldbewelcome.{noformat}Exceptioninthreadmainjava.io.IOException:Failedtovalidateaservercertificate.Ifyouareusingaself-signedcertificate,youcanusethe-noCertificateCheckoptiontobypassthischeck. athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327) athudson.remoting.Launcher.run(Launcher.java:219) athudson.remoting.Launcher.main(Launcher.java:192)Causedby:javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.ssl.Alerts.getSSLException(UnknownSource) atsun.security.ssl.SSLSocketImpl.fatal(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.ClientHandshaker.serverCertificate(UnknownSource) atsun.security.ssl.ClientHandshaker.processMessage(UnknownSource) atsun.security.ssl.Handshaker.processLoop(UnknownSource) atsun.security.ssl.Handshaker.process_record(UnknownSource) atsun.security.ssl.SSLSocketImpl.readRecord(UnknownSource) atsun.security.ssl.SSLSocketImpl.performInitialHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.net.www.protocol.https.HttpsClient.afterConnect(UnknownSource) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(UnknownSource) atsun.net.www.protocol.https.HttpsURLConnectionImpl.connect(UnknownSource) athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269) ...2moreCausedby:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.validator.PKIXValidator.doBuild(UnknownSource) atsun.security.validator.PKIXValidator.engineValidate(UnknownSource) atsun.security.validator.Validator.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.validate(UnknownSource) 

[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-21 Thread w.male...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Waldek M edited a comment on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 Samehere -althoughreasonmightbedifferent .SlavestartedonWIndows7,onanADaccount,asaservice. Dropsalmostimmediately. {noformat}java.io.IOException:Connectionaborted:org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave] atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:java.io.IOException:Connectionresetbypeer atsun.nio.ch.FileDispatcherImpl.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) atsun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) atsun.nio.ch.IOUtil.read(IOUtil.java:197) atsun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) atorg.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) atorg.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ...6more{noformat}Foundsomemoreinslave'slog.MymasterinstanceisusinghttpsandalthoughthecertificateisinstalledinWindowsandbrowsersrecognizeit,slavecomplainsaboutit-asbelow.Anyideaswouldbewelcome.{noformat}Exceptioninthreadmainjava.io.IOException:Failedtovalidateaservercertificate.Ifyouareusingaself-signedcertificate,youcanusethe-noCertificateCheckoptiontobypassthischeck. athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327) athudson.remoting.Launcher.run(Launcher.java:219) athudson.remoting.Launcher.main(Launcher.java:192)Causedby:javax.net.ssl.SSLHandshakeException:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.ssl.Alerts.getSSLException(UnknownSource) atsun.security.ssl.SSLSocketImpl.fatal(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.Handshaker.fatalSE(UnknownSource) atsun.security.ssl.ClientHandshaker.serverCertificate(UnknownSource) atsun.security.ssl.ClientHandshaker.processMessage(UnknownSource) atsun.security.ssl.Handshaker.processLoop(UnknownSource) atsun.security.ssl.Handshaker.process_record(UnknownSource) atsun.security.ssl.SSLSocketImpl.readRecord(UnknownSource) atsun.security.ssl.SSLSocketImpl.performInitialHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.security.ssl.SSLSocketImpl.startHandshake(UnknownSource) atsun.net.www.protocol.https.HttpsClient.afterConnect(UnknownSource) atsun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(UnknownSource) atsun.net.www.protocol.https.HttpsURLConnectionImpl.connect(UnknownSource) athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269) ...2moreCausedby:sun.security.validator.ValidatorException:PKIXpathbuildingfailed:sun.security.provider.certpath.SunCertPathBuilderException:unabletofindvalidcertificationpathtorequestedtarget atsun.security.validator.PKIXValidator.doBuild(UnknownSource) atsun.security.validator.PKIXValidator.engineValidate(UnknownSource) atsun.security.validator.Validator.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.validate(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.checkTrusted(UnknownSource) atsun.security.ssl.X509TrustManagerImpl.checkServerTrusted(UnknownSource) 

[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-21 Thread w.male...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Waldek M commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
Same here. Slave started on WIndows 7, on an AD account, as a service. 

 
java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@240c0b4e[name=ST_windows_slave]
	at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
Caused by: java.io.IOException: Connection reset by peer
	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
	at sun.nio.ch.IOUtil.read(IOUtil.java:197)
	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379)
	at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)
	at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561)
	... 6 more
 

 
Found some more in slave's log. My master instance is using https and although the certificate is installed in Windows and browsers recognize it, slave complains about it - as below. Any ideas would be welcome. 

 
Exception in thread main java.io.IOException: Failed to validate a server certificate. If you are using a self-signed certificate, you can use the -noCertificateCheck option to bypass this check.
	at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:327)
	at hudson.remoting.Launcher.run(Launcher.java:219)
	at hudson.remoting.Launcher.main(Launcher.java:192)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at sun.security.ssl.Alerts.getSSLException(Unknown Source)
	at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
	at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
	at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
	at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
	at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
	at sun.security.ssl.Handshaker.processLoop(Unknown Source)
	at sun.security.ssl.Handshaker.process_record(Unknown Source)
	at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
	at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
	at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:269)
	... 2 more
Caused by: 

[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-02 Thread jan.muel...@janitza.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Mller commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
We may have a similar problem. We start a windows vm and connect it via jnlp to the master, then it starts some work and after some time, usually 3-5h the slave gets disconnected unintentionally: 

 

java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@7aa84678[name=QF-WinXP]
	at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:211)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:631)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Connection reset by peer
	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
	at sun.nio.ch.IOUtil.read(IOUtil.java:197)
	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379)
	at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136)
	at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-07-02 Thread jan.muel...@janitza.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Mller edited a comment on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 Wemayhaveasimilarproblem.Westartawindowsvmandconnectitviajnlptothemaster,thenitstartssomeworkandaftersometime,usually3-5htheslavegetsdisconnectedunintentionally:{code}java.io.IOException:Connectionaborted:org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@7aa84678[name=QF-WinXP] atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:211) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:631) atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) atjava.util.concurrent.FutureTask.run(FutureTask.java:266) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) atjava.lang.Thread.run(Thread.java:745)Causedby:java.io.IOException:Connectionresetbypeer atsun.nio.ch.FileDispatcherImpl.read0(NativeMethod) atsun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) atsun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) atsun.nio.ch.IOUtil.read(IOUtil.java:197) atsun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) atorg.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) atorg.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564){code} Wehaveonlyonewindowsmachineandthismachineshowsthisbehavior.Allthelinuxslavesareconnectedconstantlywithoutanyproblems. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-05-25 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
On my slave where I see this error in the server management console I see this: 
TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint. 
I guess Jenkins is abusing the connection somehow  Any ideas how to resolve it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-05-25 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28155 
 
 
 
  Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vassilena Treneva 
 
 
 

Component/s:
 
 remoting 
 
 
 

Priority:
 
 Major Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-05-07 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28155 
 
 
 
  Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
SQL server that I have installed on this slave, has some TCP settings. By default it listens to 1433. Could that be some kind of a problem? Any ideas? SQL killing some connection? 
The post here: http://www.redmountainsw.com/wordpress/864/tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host/ provides a lot of information, but my error is not on SQL side and I don’t want to turn connection pooling off… 
 
 
 
 
 
 
 
 
 

Change By:
 
 Vassilena Treneva 
 
 
 

Attachment:
 
 sql-server-manager.jpg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-05-04 Thread dan...@beckweb.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 

I am sure it is not a network issue as I tried pinging the network from system start-up till the problem occurs.
 
Why are you so sure about this? Pinging does not keep a connection open. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-05-04 Thread vasilena.tren...@softwareag.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vassilena Treneva commented on  JENKINS-28155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Job fails with [An existing connection was forcibly closed by the remote host]  
 
 
 
 
 
 
 
 
 
 
Hi Daniel, 
I will rephrase - I am sure that pinging the master from the slave is fine as I initially suspect some kind of network failure. Do you have some suggestion that can help me debug or resolve my problem?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-04-29 Thread vasilena.tren...@softwareag.com (JIRA)














































Vassilena Treneva
 created  JENKINS-28155


Job fails with [An existing connection was forcibly closed by the remote host]















Issue Type:


Bug



Assignee:


Unassigned


Components:


core, slave-utilization



Created:


29/Apr/15 1:17 PM



Description:


Our Windows slaves are JNLP connected using scheduled tasks (like this: https://wiki.jenkins-ci.org/display/JENKINS/Launch+Java+Web+Start+slave+agent+via+Windows+Scheduler).

When a job starts working with a slave it suddenly fails because the connection was lost. It says something on slave side killed the connection. Few minutes afterwards the slave is back on-line. I am sure it is not a network issue as I tried pinging the network from system start-up till the problem occurs. I could not find find what kills the connection and disable TCP chimney (advice from google) did not work.

The exception is below.

I think proper behaviour would be not to fail the job but attempt to reconnect. Any hints of additional configuration that will help me resolve this issue is appreciated.

Building remotely on vmbam32.eur.ad.sag (R2 Server 2012 Enterprise Windows) in workspace c:\jenkins\workspace\optimize-install
FATAL: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag
hudson.remoting.RequestAbortedException: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag
	at hudson.remoting.Request.abort(Request.java:296)
	at hudson.remoting.Channel.terminate(Channel.java:815)
	at hudson.remoting.Channel$2.terminate(Channel.java:492)
	at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72)
	at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
	at ..remote call to vmbam32.eur.ad.sag(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361)
	at hudson.remoting.Request.call(Request.java:171)
	at hudson.remoting.Channel.call(Channel.java:752)
	at hudson.FilePath.act(FilePath.java:980)
	at hudson.FilePath.act(FilePath.java:969)
	at hudson.FilePath.mkdirs(FilePath.java:1152)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
	at hudson.model.Run.execute(Run.java:1744)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@b7add1name=vmbam32.eur.ad.sag
	at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208)
	at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
	at sun.nio.ch.SocketDispatcher.read0(Native Method)
	at 

[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]

2015-04-29 Thread vasilena.tren...@softwareag.com (JIRA)














































Vassilena Treneva
 updated  JENKINS-28155


Job fails with [An existing connection was forcibly closed by the remote host]
















Change By:


Vassilena Treneva
(29/Apr/15 1:20 PM)




Component/s:


windows-slaves-plugin



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.