subject:"\[JIRA\] \(JENKINS\-57244\) java.io.NotSerializableException\: The calling thread Thread has no associated channel"

Title: Message Title

rherrick commented on JENKINS-57244

Re: java.io.NotSerializableException: The calling thread Thread has no associated channel

This issue is absolutely killing our build server. It's appearing in many different contexts, including getting build configurations, viewing jobs, running executors, routine maintenance tasks like fingerprint cleanup, etc. There have been 4,707 occurrences in just the last three hours: jenkins.log is 32MB (attached compressed jenkins.log.gz). Jenkins is at 2.178. I keep upgrading hoping that this will be fixed but clearly it's not. If there's a single plugin causing the problem, I'd be happy to uninstall it but, as I noted, it's happening for lots of different operations. The biggest problem is that it's blocking the credentials store functionality, so projects that already have credentials configured have a warning "Cannot find any credentials with id ". The only options available in the credentials drop-down list are "current" and "none". If I set the credentials to "none" and save the configuration, then the only option available is "none". At some point the following message is logged: 2019-05-20 14:36:05.974+ [id=10] WARNING hudson.FilePath#_getChannelForSerialization: A FilePath object is being serialized when it should not be, indicating a bug in a plugin. See https://jenkins.io/redirect/filepath-serialization for details. java.io.NotSerializableException: The calling thread Thread[Handling GET /credentials/store/system/domain/_/credential// from __ : __ CredentialsStoreAction/CredentialsWrapper/index.jelly,5,main] has no associated channel. The current object null is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel I've got builds limping along now after dealing with weird conflicts from the authorize project plugin that may or may not be related to this issue, but I would really like a fix to this both so we can configure credentials on projects without having to edit config.xml files and to declutter the log files so that we can see any other issues that may occur.

Add Comment

This message was sent by Atlassi

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 rherrick  
 
 
Attachment: 
 jenkins.log.gz  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5572.1558373942099%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 rherrick  
 
 
Attachment: 
 jenkins.log.gz  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5565.1558373941277%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 rherrick  
 
 
Attachment: 
 jenkins.log.gz  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5579.1558373944205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 rherrick  
 
 
Attachment: 
 jenkins.log.gz  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5558.1558373880261%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 rherrick  
 
 
Attachment: 
 jenkins.log.gz  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5548.1558372860565%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-07 Thread we...@iml.fhg.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Norbert Weiß commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 As far as I understand there is some work in progress to fix the issue in the maven-plugin code.  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread mat...@mathin.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Ebert commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I think Jesse already created a bug for the scoverage plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 The core regression was fixed in Jenkins 2.166. Now it is up to plugins to implement a proper fix on their side to avoid legitimate warnings in system logs. Norbert Weiß Dan Ebert could you please create follow-up tickets for that to the plugins?  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 

  
 
 
 
 

 
  after a  successfull  successful  Execution we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem) {code:none}INFO: EXECUTION SUCCESS INFO:  INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO:  FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel  Debugging information  message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshalle

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 

  
 
 
 
 

 
  after a successfull  Excecution  Execution  we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem)   {code:none}INFO: EXECUTION SUCCESS INFO:  INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO:  FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel  Debugging information  message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshal

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 In the Gatling plugin, apparently some state was needed in the action, though the full file path was surely overkill.  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 Prepared a core patch to make these errors nonfatal, and patches for the Maven and SCoverage plugins to not attempt to store FilePath instances. (In both cases, the object referred always to a local file on the Jenkins master, so a File or String would have sufficed; and no such field was actually needed to begin with. Same in JENKINS-57229 I think.)  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I think I understand the problem in the Maven plugin, but need to write a test to reproduce it—the existing test suite, though quite large, appears to never exercise the Javadoc reporter which is the source of the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 

  
 
 
 
 

 
  after a successfull Excecution we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem)  {code:none}   INFO: EXECUTION SUCCESS INFO:  INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO:  FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel  Debugging information  message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-03 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 maven-plugin  
 
 
Component/s: 
 scoverage-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-03 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 And Maven Plugin according to the original stacktrace  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-03 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 This is a valid failure caused by JENKINS-47896 which prevents improper serialization of Remoting objects to wrong destinations. We will need a fix in the scoverage plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Ebert edited a comment on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I'm seeing a similar problem. Here's the stack trace from the build log:{{  }} {{* 07:53:56 *   hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel *  07:53:56 *    at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) *  07:53:56 *    at hudson.FilePath.writeObject(FilePath.java:2989) *  07:53:56 *    at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source) *  07:53:56 *    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) *  07:53:56 *    at java.lang.reflect.Method.invoke(Method.java:498) *  07:53:56 *    at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) *  07:53:56 *   Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel *  07:53:56 *    Debugging information  *  07:53:56 *   message : Could not call hudson.FilePath.writeObject() *  07:53:56 *   cause-exception : java.io.NotSerializableException *  07:53:56 *   cause-message   : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel *  07:53:56 *   --- *  07:53:56 *    at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) *  07:53:56 *    at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) *  07:53:56 *    at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) *  07:53:56 *    at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) *  07:53:56 *    at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) *  07:53:56 *    at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) *  07:53:56 *    at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263) *  07:53:56 *    at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250) *  07:53:56 *   Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction *  07:53:56 *    at hudson.util.RobustReflect

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-02 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Ebert commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I'm seeing a similar problem. Here's the stack trace from the build log:   07:53:56 hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)07:53:56 at hudson.FilePath.writeObject(FilePath.java:2989)07:53:56 at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source)07:53:56 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)07:53:56 at java.lang.reflect.Method.invoke(Method.java:498)07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)07:53:56 Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56*  Debugging information 07:53:56 message : Could not call hudson.FilePath.writeObject()07:53:56 cause-exception : java.io.NotSerializableException*07:53:56* cause-message : The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* ---07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)07:53:56 at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)07:53:56 at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)07:53:56 at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)07:53:56 at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)07:53:56 at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)07:53:56 at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)07:53:56 Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254)07:53:56 at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:222)07:53:56 at com.thoughtworks.xstream.converters.reflection.PureJavaReflect

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Ebert edited a comment on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I'm seeing a similar problem. Here's the stack trace from the build log:{{ }}{{ }} *07:53:56*  hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56*   at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)*07:53:56*   at hudson.FilePath.writeObject(FilePath.java:2989)*07:53:56*   at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source)*07:53:56*   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*07:53:56*   at java.lang.reflect.Method.invoke(Method.java:498)*07:53:56*   at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)*07:53:56*  Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56*   Debugging information *07:53:56*  message : Could not call hudson.FilePath.writeObject()*07:53:56*  cause-exception : java.io.NotSerializableException*07:53:56*  cause-message   : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56*  ---*07:53:56*   at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)*07:53:56*   at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)*07:53:56*   at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)*07:53:56*   at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)*07:53:56*   at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)*07:53:56*   at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)*07:53:56*   at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)*07:53:56*   at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)*07:53:56*  Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction*07:53:56*   at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254)*07:53:56*   at hudson.util.RobustReflectionConver

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel