[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jagjeet Chadha edited a comment on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Can anyone tell me how o fix the mentioned issue? I have started seeing the same error on Jenkins 2.213 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188450.151859845.7860.1578986460401%40Atlassian.JIRA.
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jagjeet Chadha commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Can anyone tell me how o fix the mentioned issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188450.151859845.7847.1578986400377%40Atlassian.JIRA.
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Gustav Moelschl commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed We had exactly the same problem with our Windows slaves. We were starting them by a Java command line using the Windows Task Scheduler and after a few days we got the errors. We solved it by configuring all Windows slaves as a Windows service. See https://wiki.jenkins.io/display/JENKINS/Step+by+step+guide+to+set+up+master+and+agent+machines+on+Windows Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188450.151859845.4167.1570687860519%40Atlassian.JIRA.
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jason Woodgate commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Also receiving this error, running the current latest released build (v5.139.2). Any news on a fix? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Andy Nelsen commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed I'm seeing this same issue in tfs-plugin v5.142.0 where the slave reports WARNING: LinkageError while performing UserRequest:hudson.plugins.tfs.commands.RemoteChangesetVersionCommand and then the slave-agent is toast until the Jenkins service is restarted on the agent It seems like there was a potential "private fix" for this issue. Was that fix ever committed and released? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Josh Soref commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Fwiw, the two warnings in are addressed by JENKINS-50457 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Stefan Drissen commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed With the private build, the agent is now surviving death by changeset -1: Building remotely on in workspace c:\jenkins\workspace\\\publish_browser-codedui Checking if there exists a mapping for c:\jenkins\workspace\\\publish_browser-codedui...yes, in workspace 'Jenkins---publish_browser-codedui-'. Downloading list of workspaces from ... Getting version 'C2147483647' to 'c:\jenkins\workspace\\\publish_browser-codedui'... FATAL: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF14019: The changeset 2147483647 does not exist. hudson.remoting.ProxyException: com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: TF14019: The changeset 2147483647 does not exist. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._Repository5Soap12Service.get(_Repository5Soap12Service.java:109) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.get(WebServiceLayer.java:941) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.34.30/10.2.34.30:55027 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at hudson.plugins.tfs.model.Server.execute(Server.java:233) at hudson.plugins.tfs.model.Project.getFiles(Project.java:278) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:66) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:458) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused: hudson.remoting.ProxyException: com.microsoft.tfs.core.exceptions.TECoreException: TF14019: The changeset 2147483647 does not exist. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.get(WebServiceLayer.java:980) at
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Stefan Drissen edited a comment on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Hi Jason,Did you get my e-mail? I see that your e-mail and last name do not seem to match (1t vs 2t). Just tried 2ts and that's immediately bounced. Kind regards, Stefan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Stefan Drissen commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Hi Jason, Did you get my e-mail? I see that your e-mail and last name do not seem to match (1t vs 2t). Kind regards, Stefan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jason Prickett edited a comment on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed [~smd], Thanks for providing the callstack! It looks like we should probably handle this error a bit better and not let it leak out. If you are willing to try a private fix, email me at jpricketmicrosoft.com and I will provide you with a private fix. Of course, I guess you won't know if the problem is fixed for a few days/weeks. But I would still like to have you verify the fix directly if possible.Thanks, Jason Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Jason Prickett commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Thanks for providing the callstack! It looks like we should probably handle this error a bit better and not let it leak out. If you are willing to try a private fix, email me at jpricketmicrosoft.com and I will provide you with a private fix. Of course, I guess you won't know if the problem is fixed for a few days/weeks. But I would still like to have you verify the fix directly if possible. Thanks, Jason Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49546
java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Change By:
Stefan Drissen
Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time.The agents are started via the Windows Task Scheduler.Complete log:{code:java}Started by upstream project "/build work" build number 325originally caused by:Started by an SCM change[EnvInject] - Loading node environment variables.Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ieFATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failedAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:909)at hudson.plugins.tfs.model.Server.execute(Server.java:233)at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1203)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136)at hudson.model.Run.execute(Run.java:1727)at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.NoClassDefFoundError: Could not initialize class com.microsoft.tfs.core.config.persistence.DefaultPersistenceStoreProviderat hudson.plugins.tfs.model.Server.(Server.java:119)at hudson.plugins.tfs.commands.AbstractCallableCommand.createServer(AbstractCallableCommand.java:45)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:56)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)at hudson.remoting.UserRequest.perform(UserRequest.java:210)at
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49546
java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Change By:
Stefan Drissen
Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time.The agents are started via the Windows Task Scheduler.Complete log:{code:java}Started by upstream project "/build work" build number 325originally caused by:Started by an SCM change[EnvInject] - Loading node environment variables.Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ieFATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failedAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:909)at hudson.plugins.tfs.model.Server.execute(Server.java:233)at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1203)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136)at hudson.model.Run.execute(Run.java:1727)at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.NoClassDefFoundError: Could not initialize class com.microsoft.tfs.core.config.persistence.DefaultPersistenceStoreProviderat hudson.plugins.tfs.model.Server.(Server.java:119)at hudson.plugins.tfs.commands.AbstractCallableCommand.createServer(AbstractCallableCommand.java:45)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:56)at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)at hudson.remoting.UserRequest.perform(UserRequest.java:210)at
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Stefan Drissen created an issue Jenkins / JENKINS-49546 java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2018-02-14 08:54 Environment: Windows 2012R2 x64 Java 1.8.0_161 x64 Jenkins 2.105 TFS-plugni 5.126.0 Labels: slave plugin windows Priority: Critical Reporter: Stefan Drissen Since upgrading from the pre-Java SDK TFS-plugin (3.2) to the latest plugin (5.126.0) I am needing to tickle my agents every now and then. They will work fine for a few days and then suddenly one will start throwing the above error. Once in this state, that agent never recovers and the Jenkins agent task needs to be restarted. That agent will then behave for some time. The agents are started via the Windows Task Scheduler. Complete log: Started by upstream project "/build work" build number 325 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on (coded_ui_oe) in workspace c:\jenkins\workspace\\work\coded.ui_run.all.tests.ie FATAL: java.io.IOException: Remote call on JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 failed Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.2.33.142/10.2.33.142:4028 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1696)
