[JENKINS-26137] Mysterious serialization errors - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Component/s: workflow-support-plugin
Labels:

Similar Issues:

Show

Description

A flow which just had

node('...') {sh 'echo hi'}

waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with

...
Running: Allocate node : End
Running: End of Workflow
java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:10S18)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584)
	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
	at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181)
	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:745)
	at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)
Caused by: an exception which occurred:
	in field task
	in object java.util.ArrayList@401ac88
Finished: FAILURE

CpsStepContext.getThread then began complaining that

    no thread 2 among []

as the DurableTaskStep$Execution.run kept on running.

It is not apparent from this stack trace why something is trying to serialize the job.

Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was ExecutorPickle. But why could the error message not say that? It only said field task, which was not enough information.

Attachments

Issue Links

is blocking

JENKINS-40109 Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector

Resolved

JENKINS-26051 Workflow integration for Credentials Binding

Resolved

is duplicated by

JENKINS-41770 CPS serialization failure doesn't provide useful information

Resolved

is related to

JENKINS-25925 More polite reporting of NotSerializableException

Open

links to

CloudBees Internal CD-40

jboss-marshalling PR 37

PR 37

workflow-basic-steps PR 39

(3 links to)

Activity

Ascending order - Click to sort in descending order

Jesse Glick created issue - 2014-12-17 17:36

Jesse Glick made changes - 2014-12-17 17:37

Field	Original Value	New Value
Link		This issue is related to JENKINS-25925 [ JENKINS-25925 ]

Jesse Glick made changes - 2015-01-12 20:28

Link

This issue is blocking ~~JENKINS-26051~~ [ ~~JENKINS-26051~~ ]

Jesse Glick made changes - 2015-11-12 17:03

Priority

Minor [ 4 ]

Major [ 3 ]

Thomas Goeppel made changes - 2016-05-12 04:50

Description

A flow which just had

{code}
node('...') {sh 'echo hi'}
{code}

waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with

{code:none}
...
Running: Allocate node : End
Running: End of Workflow
java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1018)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181)
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:745)
at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)
Caused by: an exception which occurred:
in field task
in object java.util.ArrayList@401ac88
Finished: FAILURE
{code}

{{CpsStepContext.getThread}} then began complaining that

{code:none}
no thread 2 among []
{code}

as the {{DurableTaskStep$Execution.run}} kept on running.

It is not apparent from this stack trace why something is trying to serialize the job.

Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was {{ExecutorPickle}}. But why could the error message not say that? It only said {{field task}}, which was not enough information.

A flow which just had

{code}
node('...') {sh 'echo hi'}
{code}

waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with

{code:none}
...
Running: Allocate node : End
Running: End of Workflow
java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:10S18)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181)
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:745)
at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)
Caused by: an exception which occurred:
in field task
in object java.util.ArrayList@401ac88
Finished: FAILURE
{code}

{{CpsStepContext.getThread}} then began complaining that

{code:none}
no thread 2 among []
{code}

as the {{DurableTaskStep$Execution.run}} kept on running.

It is not apparent from this stack trace why something is trying to serialize the job.

Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was {{ExecutorPickle}}. But why could the error message not say that? It only said {{field task}}, which was not enough information.

Jesse Glick made changes - 2016-06-06 21:26

Epic Link

JENKINS-35396 [ 171189 ]

R. Tyler Croy made changes - 2016-07-25 23:51

Workflow

JNJira [ 160127 ]

JNJira + In-Review [ 180261 ]

Andrew Bayer made changes - 2016-08-26 21:49

Component/s

pipeline-general [ 21692 ]

Andrew Bayer made changes - 2016-08-26 21:54

Component/s

workflow-plugin [ 18820 ]

Jesse Glick made changes - 2016-08-29 17:18

Component/s		workflow-support-plugin [ 21719 ]
Component/s	pipeline [ 21692 ]

Mor L made changes - 2016-12-01 11:59

Comment

[ Or better yet - pipeline should start supporting all the data structures that are supported in groovy :)
This includes (from the list of non-serialized objects I encountered so far): maps, xmlSlurper and sun.net.www.protocol.https.HttpsURLConnectionImpl ]

Jesse Glick made changes - 2017-02-13 22:24

Link

This issue is duplicated by ~~JENKINS-41770~~ [ ~~JENKINS-41770~~ ]

Kohsuke Kawaguchi made changes - 2017-03-01 03:16

Labels

robustness

kohsuke-plane-project robustness

Jesse Glick made changes - 2017-03-01 21:19

Labels

kohsuke-plane-project robustness

diagnostics kohsuke-plane-project robustness

Jesse Glick made changes - 2017-03-24 02:27

Remote Link

This issue links to "workflow-basic-steps PR 39 (Web Link)" [ 15812 ]

Jesse Glick made changes - 2017-03-24 18:42

Link

This issue is blocking ~~JENKINS-40109~~ [ ~~JENKINS-40109~~ ]

Jesse Glick made changes - 2017-06-20 21:05

Remote Link

This issue links to "jboss-marshalling PR 37 (Web Link)" [ 17156 ]

Jesse Glick made changes - 2017-06-20 21:28

Assignee

Kohsuke Kawaguchi [ kohsuke ]

Jesse Glick [ jglick ]

Jesse Glick made changes - 2017-06-20 21:28

Status

Open [ 1 ]

In Progress [ 3 ]

Jesse Glick made changes - 2017-06-20 22:57

Remote Link

This issue links to "PR 37 (Web Link)" [ 17158 ]

Jesse Glick made changes - 2017-06-20 22:57

Status

In Progress [ 3 ]

In Review [ 10005 ]

Jesse Glick made changes - 2017-06-21 19:47

Resolution		Fixed [ 1 ]
Status	In Review [ 10005 ]	Resolved [ 5 ]

Sam Van Oort made changes - 2017-09-26 22:22

Status

Resolved [ 5 ]

Closed [ 6 ]

CloudBees Inc. made changes - 2017-12-05 09:56

Remote Link

This issue links to "CloudBees Internal CD-40 (Web Link)" [ 19133 ]

Marky Jackson made changes - 2020-06-07 15:55

Epic Link

JENKINS-35396 [ 171189 ]

People

Assignee:: Jesse Glick

Reporter:: Jesse Glick

Votes:: 1 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 2014-12-17 17:36

Updated:: 2020-06-07 15:55

Resolved:: 2017-06-21 19:47