[JIRA] (JENKINS-39800) Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException

4 views
Skip to first unread message

klogan@enova.com (JIRA)

unread,
Nov 16, 2016, 6:30:01 PM11/16/16
to jenkinsc...@googlegroups.com
Kevin Logan created an issue
 
Jenkins / Bug JENKINS-39800
Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2016/Nov/16 11:29 PM
Environment: Debian Wheezy, Jenkins 2.7.2, oracle-java8-server-jre 8u111-wheezy1
Priority: Major Major
Reporter: Kevin Logan

Successful builds will fail seemingly at random with the below exception.

Started by timer
[EnvInject] - Loading node environment variables.
Building in workspace <http://modok-auto.oak.enova.com/job/CA-Colossus_Monitor/ws/>
[workspace] $ /bin/sh -xe /tmp/hudson7219746524057295462.sh
+ ruby /etc/git/automation_scripts/ruby/colossus_monitor.rb ca
-0.006550645982850592
FATAL: null
java.lang.ArrayIndexOutOfBoundsException
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:233)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744)
at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:462)
at hudson.util.ProcessTree$Linux.readFileToByteArray(ProcessTree.java:745)
at hudson.util.ProcessTree$Linux$LinuxProcess.getEnvironmentVariables(ProcessTree.java:725)
at hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:277)
at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:513)
at hudson.Launcher$LocalLauncher.kill(Launcher.java:838)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Nov 19, 2016, 5:28:01 PM11/19/16
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Nov 19, 2016, 6:49:01 PM11/19/16
to jenkinsc...@googlegroups.com

What happens when a process quits between Jenkins deciding to check its env vars, and looking at the proc file?

klogan@enova.com (JIRA)

unread,
Nov 21, 2016, 4:44:03 PM11/21/16
to jenkinsc...@googlegroups.com

If it helps any we upgraded Jenkins from 1.653 and Java from 6b38-1.13.10-1~deb7u1 when this problem started.

klogan@enova.com (JIRA)

unread,
Jan 8, 2017, 8:47:02 PM1/8/17
to jenkinsc...@googlegroups.com

Has anyone been able to look at this? It's been a while with no response. Daniel Beck I believe that is what is causing this error when I was looking through the code, but I'm not great with java. Any ideas on a possible workaround?

dbeck@cloudbees.com (JIRA)

unread,
Jan 8, 2017, 8:52:02 PM1/8/17
to jenkinsc...@googlegroups.com

Don't continue the process past the lifetime of its invoking shell. If my guess is true, and the problem is that Jenkins is trying to kill a process that suddenly stops existing, don't make it kill it by quitting in time.

klogan@enova.com (JIRA)

unread,
Jan 10, 2017, 6:18:01 PM1/10/17
to jenkinsc...@googlegroups.com
Kevin Logan updated an issue
 
Change By: Kevin Logan
Attachment: Screen Shot 2017-01-10 at 5.16.28 PM.png

mpescetto@enova.com (JIRA)

unread,
Jan 24, 2017, 1:59:03 PM1/24/17
to jenkinsc...@googlegroups.com
Mike Pescetto updated an issue
Change By: Mike Pescetto

mpescetto@enova.com (JIRA)

unread,
Jan 24, 2017, 2:06:02 PM1/24/17
to jenkinsc...@googlegroups.com
Mike Pescetto commented on Bug JENKINS-39800
 
Re: Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException

Hi Daniel Beck,

Can you elaborate on what settings might have to be adjusted for your proposed workaround? Prior to the Jenkins 2.7.2 upgrade, 1.653 did not exhibit this issue.

Thank you,
~Mike

mpescetto@enova.com (JIRA)

unread,
Feb 2, 2017, 5:33:02 PM2/2/17
to jenkinsc...@googlegroups.com

Hi Daniel Beck,
Can you please elaborate on what settings might have to be adjusted for your proposed workaround? Prior to the Jenkins 2.7.2 upgrade, 1.653 did not exhibit this issue.
Thank you,
~Mike

eyal1.david@intel.com (JIRA)

unread,
Mar 5, 2017, 5:26:02 AM3/5/17
to jenkinsc...@googlegroups.com

Hi having the same problem here can anyone share how to workaround it or how to fix ?

 

any road map for this issue ?

Thanks
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

1petemoore@gmail.com (JIRA)

unread,
Nov 6, 2019, 9:34:03 AM11/6/19
to jenkinsc...@googlegroups.com

I get this when i try to make a report that has more than 250 steps.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages