[JENKINS-56028] StackOverflowError after workflow-support upgrade

Type: Bug
Resolution: Duplicate
Priority: Critical
Component/s: workflow-support-plugin
Labels:
None
Environment:
Jenkins 2.16, Pipeline Support APIs 3.2

Similar Issues:
Powered by SuggestiMate

Show
Epic Link:
Pipeline Durability

After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin changelog but with all runs.

How to reproduce

Update to workflow support plugin version >= 3.0
Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

Expected behavior

Pipeline works as before the update

Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

[Pipeline] {
[Pipeline] End of Pipelinejava.lang.StackOverflowError
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)

The job ends but still occupies the agent slot.

Additional information

We are using Multibranch Pipeline to automatically build all our branches
Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during mvn install or during the frontend installation
There is an option retry(3) right before the problem. This is the next thing I will check.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

Jenkinsfile-reduced.txt
3 kB
2019-02-07 16:30

duplicates

JENKINS-52966 Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError

Open

Michael Cornel created issue - 2019-02-07 16:36

Michael Cornel made changes - 2019-02-07 16:36

Epic Link

New: JENKINS-35399 [ 171192 ]

Michael Cornel made changes - 2019-02-07 16:38

Component/s		New: workflow-support-plugin [ 21719 ]
Component/s	Original: pipeline-library [ 23622 ]
Key	Original: ~~INFRA-2003~~	New: ~~JENKINS-56028~~
Workflow	Original: classic default workflow [ 234853 ]	New: JNJira + In-Review [ 234854 ]
Project	Original: Infrastructure [ 10301 ]	New: Jenkins [ 10172 ]

Michael Cornel made changes - 2019-02-07 16:39

Description

Original: After upgrading the pipeline support APIs addon to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the [addon changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to pipeline support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:
[Pipeline] {[Pipeline] End of Pipelinejava.lang.StackOverflowError
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
The job ends but still occupies the agent slot.
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

New: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:
[Pipeline] {[Pipeline] End of Pipelinejava.lang.StackOverflowError
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
The job ends but still occupies the agent slot.
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

Michael Cornel made changes - 2019-02-07 16:40

Assignee

Original: R. Tyler Croy [ rtyler ]

Michael Cornel made changes - 2019-02-07 16:40

Description

Original: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:
[Pipeline] {[Pipeline] End of Pipelinejava.lang.StackOverflowError
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)
The job ends but still occupies the agent slot.
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

New: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

{{[Pipeline] {}}
{{[Pipeline] End of Pipelinejava.lang.StackOverflowError}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)}}
{{ The job ends but still occupies the agent slot.}}
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

Michael Cornel made changes - 2019-02-07 16:41

Description

Original: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

{{[Pipeline] {}}
{{[Pipeline] End of Pipelinejava.lang.StackOverflowError}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)}}
{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)}}
{{ The job ends but still occupies the agent slot.}}
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

New: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

{{[Pipeline] {}}
{{[Pipeline] End of Pipelinejava.lang.StackOverflowError}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114) }}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)}}
\{{ The job ends but still occupies the agent slot.}}
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

Michael Cornel made changes - 2019-02-07 16:41

Description

Original: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

{{[Pipeline] {}}
{{[Pipeline] End of Pipelinejava.lang.StackOverflowError}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114) }}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)}}
\{{ at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)}}
\{{ The job ends but still occupies the agent slot.}}
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

New: After upgrading the workflow support APIs plugin to version 3.0 or version 3.2 our pipeline does not work any more. The problem is not about pipelines running during the upgrade as mentioned in the plugin [changelog|https://plugins.jenkins.io/workflow-support] but with all runs.
h2. How to reproduce
# Update to workflow support plugin version >= 3.0
# Run a build with our Jenkinsfile (I attached a file removing all parts I think are not relevant)

h2. Expected behavior

Pipeline works as before the update
h2. Actual behavior

Pipeline works in the beginning but then exits with a StackOverflowError:

{{[Pipeline] {}}
{{[Pipeline] End of Pipelinejava.lang.StackOverflowError}}
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920)

The job ends but still occupies the agent slot.
h2. Additional information
* We are using Multibranch Pipeline to automatically build all our branches
* Downgrading the plugin helped last time but does not work any more as now other plugins depend on the new version.
* It appears that the error occurs at the same time. However, since this is a parallel stage I am not sure if it is during {{mvn install}} or during the frontend installation
* There is an {{option retry(3)}} right before the problem. This is the next thing I will check.

Michael Cornel made changes - 2019-02-07 16:49

Assignee

New: Devin Nusbaum [ dnusbaum ]

Devin Nusbaum made changes - 2019-02-07 17:04

Link

New: This issue duplicates JENKINS-52966 [ JENKINS-52966 ]

Devin Nusbaum made changes - 2019-02-07 17:04

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Assignee:: Devin Nusbaum

Reporter:: Michael Cornel

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2019-02-07 16:36

Updated:: 2019-02-07 17:04

Resolved:: 2019-02-07 17:04

Jenkins

Details

Description

How to reproduce

Expected behavior

Actual behavior

Additional information

Attachments

Attachments

Issue Links

Activity

People

Dates