[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title
Alexander Moiseenko updated an issue
Jenkins / JENKINS-60951
NPE Generic Webhook trigger plugin invoke
Change By:
Alexander Moiseenko
At some moment and until reboot all http requests like {{ [http://$|http://%24/]{JENKINS_URL}/generic-webhook-trigger/invoke?token=anything }} started to response with 500 error code and stacktrace:{noformat}java.lang.NullPointerException at org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty.getTriggersMap(PipelineTriggersJobProperty.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowJob.getTriggers(WorkflowJob.java:425) at org.jenkinsci.plugins.gwt.jobfinder.JobFinder.findAllJobsWithTrigger(JobFinder.java:35) at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:96) at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:56) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitorin
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title
Alexander Moiseenko created an issue
Jenkins / JENKINS-60951
NPE Generic Webhook trigger plugin invoke
Issue Type:
Bug
Assignee:
Tomas Bjerre
Components:
generic-webhook-trigger-plugin, workflow-job-plugin
Created:
2020-02-03 14:55
Environment:
Jenkins 2.176.3
Priority:
Minor
Reporter:
Alexander Moiseenko
At some moment and until reboot all http requests like {{http://$ {JENKINS_URL} /generic-webhook-trigger/invoke?token=anything}} started to response with 500 error code and stacktrace:
java.lang.NullPointerException
at org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty.getTriggersMap(PipelineTriggersJobProperty.java:133)
at org.jenkinsci.plugins.workflow.job.WorkflowJob.getTriggers(WorkflowJob.java:425)
at org.jenkinsci.plugins.gwt.jobfinder.JobFinder.findAllJobsWithTrigger(JobFinder.java:35)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:96)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:56)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stap
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: Alexander Moiseenko Attachment: thread-dump.txt 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.190959.1527520483000.73.1577359740972%40Atlassian.JIRA.
[JIRA] (JENKINS-60053) Create null diff file on config history
Title: Message Title Alexander Moiseenko commented on JENKINS-60053 Re: Create null diff file on config history Possibly duplicates JENKINS-57837 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.202883.1572928345000.11232.1573223820187%40Atlassian.JIRA.
[JIRA] (JENKINS-30446) Recursive variable substitution
Title: Message Title Alexander Moiseenko commented on JENKINS-30446 Re: Recursive variable substitution Faced the same error in freestyle job when evninject is set twice: in General section of job config and in a build step. with 50% chance build stuck on envinject build step, fills heap memory with an int[] objects, gc reaches overhead threshold, and Full GC runs frequently. Workaround: 1. kill problem thread through javamelody (Monitoring Plugin,) in our case it was in RUNNING state on: at java.util.Arrays.copyOf(Arrays.java:3332) 2. Move all envinject parametes into one call (we have move all into buld step) 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.165043.1442262821000..1571244540213%40Atlassian.JIRA.
[JIRA] (JENKINS-59194) Jenkins Queue freeze on AbstractCloudSlave.terminate
Title: Message Title Alexander Moiseenko created an issue Jenkins / JENKINS-59194 Jenkins Queue freeze on AbstractCloudSlave.terminate Issue Type: Bug Assignee: Unassigned Attachments: stacktrace.txt Components: core, durable-task-plugin, kubernetes-plugin Created: 2019-09-02 19:42 Environment: core 2.176.2 kubernetes 2.18.1 durable task plugin 1.30 Priority: Major Reporter: Alexander Moiseenko Jenkins master freeze on hudson.model.Queue.withLock. At certain moment all jobs have been stucked in waiting state, locked by java.util.concurrent.locks.ReentrantLock without any progress for 20 minutes until jenkins was restarted: "Computer.threadPoolForRemoting [#26557] / waiting for JNLP4-connect connection from 10.116.113.11/10.116.113.11:35228 id=20559800" #9908709 daemon prio=5 os_prio=0 tid=0x7f30602ca000 nid=0x4609 in Object.wait() [0x7f3120f8b000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) - locked <0x0004ea5957f0> (a hudson.remoting.UserRequest) at hudson.remoting.Channel.call(Channel.java:956) at org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:263) at hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) at org.jenkinsci.plugins.durabletask.executor
[JIRA] (JENKINS-56649) Web interface hangs on retrieve users from ldap
Title: Message Title Alexander Moiseenko created an issue Jenkins / JENKINS-56649 Web interface hangs on retrieve users from ldap Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: threaddump-1552923377339.tdump Components: active-directory-plugin Created: 2019-03-20 20:25 Environment: Jenkins 2.138.2 active directory 2.12 Priority: Minor Reporter: Alexander Moiseenko We faced web interface hang once, http requests stucked on ad user retrieve: "Handling GET /jenkins/job/PPRB_DevOps/job/Install_EIP/job/Install_EIP_2_cli/19070/wfapi from 10.116.113.11 : qtp385242642-12688644" - Thread t@12688644"Handling GET /jenkins/job/PPRB_DevOps/job/Install_EIP/job/Install_EIP_2_cli/19070/wfapi from 10.116.113.11 : qtp385242642-12688644" - Thread t@12688644 java.lang.Thread.State: WAITING at sun.misc.Unsafe.park(Native Method) - parking to wait for <83657e2> (a com.google.common.util.concurrent.AbstractFuture$Sync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304) at com.google.common.util.concurrent.AbstractFutu
[JIRA] (JENKINS-55712) SocketTimeoutException with kubernetes pipelines
Title: Message Title Alexander Moiseenko commented on JENKINS-55712 Re: SocketTimeoutException with kubernetes pipelines Possibly duplicates JENKINS-53532 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-55700) deadlock remoting TCP agent connection handler
Title: Message Title
Alexander Moiseenko updated an issue
Jenkins / JENKINS-55700
deadlock remoting TCP agent connection handler
Change By:
Alexander Moiseenko
{noformat}Found one Java-level deadlock:="TCP agent connection handler #159021 with /10.116.113.11:54776": waiting for ownable synchronizer 0x0002ce4a6770, (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), which is held by "IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.116.241.122:8181 remote=10.116.113.11/10.116.113.11:54776]] / Computer.threadPoolForRemoting [#12366]""IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.116.241.122:8181 remote=10.116.113.11/10.116.113.11:54776]] / Computer.threadPoolForRemoting [#12366]": waiting to lock monitor 0x7f75cc5900f8 (object 0x0002ce4de778, a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer), which is held by "TCP agent connection handler #159021 with /10.116.113.11:54776"Java stack information for the threads listed above:==="TCP agent connection handler #159021 with /10.116.113.11:54776": at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x0002ce4a6770> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283) at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.getNextSend(ProtocolStack.java:857) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:686) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:518) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) - locked <0x0002ce4a6800> (a java.lang.Object) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:692) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.doSend(ConnectionHeadersFilterLayer.java:497) - locked <0x0002ce4de778> (a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:692) at org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.start(ChannelApplicationLayer.java:230) at org.jenkinsci.remoting.protocol.ProtocolStack.init(ProtocolStack.java:201) at org.jenkinsci.
[JIRA] (JENKINS-55700) deadlock remoting TCP agent connection handler
Title: Message Title Alexander Moiseenko created an issue Jenkins / JENKINS-55700 deadlock remoting TCP agent connection handler Issue Type: Bug Assignee: Jeff Thompson Attachments: jenkins.tdump Components: remoting Created: 2019-01-21 12:27 Environment: Server: Jenkins 2.138.2 Remoting: 3.25 Java: 1.8.181 Labels: deadlock remoting Priority: Minor Reporter: Alexander Moiseenko Add Comment
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko stopped work on JENKINS-51568 Change By: Alexander Moiseenko Status: In Progress Open 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title
Alexander Moiseenko edited a comment on JENKINS-51568
Re: Pipeline jobs hanging in Build Executor even if it is finished
I think we've found root cause of a problem. Broken `sleep` and `timeout` methods and executor hanging all relates to jenkins.util.Timer threads. In During hang state we cojvisualvm and watch threads state looks like this :!BusyTimers.png!And in normal case:!NormalCase.PNG! In [^thread-dump.txt] we could find find can see jenkins.util.Timer stack traces, in our case the root cause was logfilesizechecker plugin, [https://github.com/jenkinsci/logfilesizechecker-plugin/blob/master/src/main/java/hudson/plugins/logfilesizechecker/LogfilesizecheckerWrapper.java#L78]that uses timer every second to check log size and this operation creates additional cpu load : {noformat}"jenkins.util.Timer [#9]" - Thread t@267 java.lang.Thread.State: RUNNABLEat java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)at java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:682)at java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:781)at java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1546)at jenkins.model.Nodes.getNode(Nodes.java:295)at jenkins.model.Jenkins.getNode(Jenkins.java:2058)at hudson.model.Computer.getNode(Computer.java:590)at hudson.slaves.SlaveComputer.getNode(SlaveComputer.java:199)at hudson.slaves.SlaveComputer.getNode(SlaveComputer.java:96)at jenkins.model.Jenkins$7.compare(Jenkins.java:1927)at jenkins.model.Jenkins$7.compare(Jenkins.java:1925)at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360)at java.util.TimSort.sort(TimSort.java:234)at java.util.Arrays.sort(Arrays.java:1438)at jenkins.model.Jenkins.getComputers(Jenkins.java:1925)at hudson.model.Executor.of(Executor.java:941)at hudson.model.Run.getExecutor(Run.java:530)at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:107)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers:- locked <4dd03582> (a java.util.concurrent.ThreadPoolExecutor$Worker) {noformat} Our jenkins.util.Timer threads are mostly in park state and sleep works fine, since we've changed DELAY value from 1 second to 10 in [https://github.com/jenkinsci/logfilesizechecker-plugin/blob/master/src/main/java/hudson/plugins/logfilesizechecker/LogfilesizecheckerWrapper.java#L46]
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished I think we've found root cause of a problem. Broken `sleep` and `timeout` methods and executor hanging all relates to jenkins.util.Timer threads. In hang state we cojvisualvm and watch threads state like this: And in normal case: In thread-dump.txt we could find find jenkins.util.Timer stack traces, in our case the root cause was logfilesizechecker plugin, https://github.com/jenkinsci/logfilesizechecker-plugin/blob/master/src/main/java/hudson/plugins/logfilesizechecker/LogfilesizecheckerWrapper.java#L78 that uses timer every second to check log size and this operation creates additional cpu load "jenkins.util.Timer [#9]" - Thread t@267 java.lang.Thread.State: RUNNABLE at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655) at java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:682) at java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:781) at java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1546) at jenkins.model.Nodes.getNode(Nodes.java:295) at jenkins.model.Jenkins.getNode(Jenkins.java:2058) at hudson.model.Computer.getNode(Computer.java:590) at hudson.slaves.SlaveComputer.getNode(SlaveComputer.java:199) at hudson.slaves.SlaveComputer.getNode(SlaveComputer.java:96) at jenkins.model.Jenkins$7.compare(Jenkins.java:1927) at jenkins.model.Jenkins$7.compare(Jenkins.java:1925) at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360) at java.util.TimSort.sort(TimSort.java:234) at java.util.Arrays.sort(Arrays.java:1438) at jenkins.model.Jenkins.getComputers(Jenkins.java:1925) at hudson.model.Executor.of(Executor.java:941) at hudson.model.Run.getExecutor(Run.java:530) at hudson.plugins.logfilesizechecker.LogfilesizecheckerWrapper$LogSizeTimerTask.doRun(LogfilesizecheckerWrapper.java:107) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Locked ownable synchronizers: - locked <4dd03582> (a java.util.concurrent.ThreadPoolExecutor$Worker) Our jenkins.util.Timer threads are mostly in park state and sleep works fine, since we've changed DELAY value from 1 second to 10 in https://github.com/jenkinsci/logfilesizechecker-plugin/blob/master/src/main/java/hudson/plugins/logfilesizechecker/LogfilesizecheckerWrapper.java#L46
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: Alexander Moiseenko Attachment: NormalCase.PNG 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: Alexander Moiseenko Attachment: BusyTimers.png 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title
Alexander Moiseenko commented on JENKINS-51568
Re: Pipeline jobs hanging in Build Executor even if it is finished
Hello. Same problem again, our new env: Jenkins 2.121.1, Pipeline Groovy 2.55 Pipeline: job 2.26 Durable Task Plugin: 1.26 Pipeline Nodes and Processes: 2.22 workaround script doesn't help anymore, after durable task plugin update probably. We've created simple pipeline job with `sleep` step to check if problem have reappered again:
pipeline {
options {
timeout(time: 60, unit: 'SECONDS')
}
stages {
stage('sleep') {
steps {
sleep 5
}
}
}
}
which finishes successfully in normal case and fails when executors gets stuck
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-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Alexander Moiseenko commented on JENKINS-54038 Re: Jacoco creates multiple Coverage reports and Trends graphs We faced the same problem after update from jacoco plugin 3.0.1 to 3.0.3, jenkins core 2.121.1 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-53665) Micro Focus Application Automation Tools - file descriptor leak
Title: Message Title
Alexander Moiseenko created an issue
Jenkins / JENKINS-53665
Micro Focus Application Automation Tools - file descriptor leak
Issue Type:
Bug
Assignee:
Daniel Gront
Attachments:
jenkins-fds.png, lsof-jenkins.zip
Components:
hp-application-automation-tools-plugin
Created:
2018-09-19 16:52
Environment:
jenkins 2.121.1
Priority:
Minor
Reporter:
Alexander Moiseenko
At some point in time, with the increase in the number of builds on Jenkins, we faced a "Too many open files" exception in Jenkins log. Analysis of lsof command output (lsof-jenkins.zip) showed that there are a lot of open files in some projects (Freestyle or Maven type) created at build completion on Jenkins master with name:
{$JENKINS_HOME}/jobs/test_project/builds/140/GetJUnitTestResults4300391778772244764.tmp
I found file with non zero size with the folowing content:
$ cat GetJUnitTestResults1715785790472604747.tmp
▒▒ ♣sr Gcom.hpe.application.automation.tools.octane.tests.junit.JUnitTestResult▒▒▒ JdurationJ startedL classNamet Ljava/lang/String;L ◄externalReportUrlq ~ L
moduleNameq ~ L pack
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished At the same time I see, that sleep step is not working properly too: simple job, that delays for 5 seconds and finish runs for hours: 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: Alexander Moiseenko Attachment: sleep-test-script.PNG 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-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Alexander Moiseenko created an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Issue Type: Bug Assignee: Unassigned Attachments: build-pipeline-steps.PNG, finished-build.PNG, stuck-executor.png Components: pipeline Created: 2018-05-28 15:14 Environment: jenkins 2.89.4 EL7 Priority: Major Reporter: Alexander Moiseenko We have huge Jenkins instance, which runs about 20k builds a day. At some moment after couple days without restart of jenkins master, pipeline jobs starts to hang executors after build finish. Freestyle and maven jobs works fine. Busy executor looks like: But build status is "finished": There are records about start and finish build in jenkins.log, but executor wasn't released at May 28, 2018 4:35:14 PM: May 28, 2018 4:28:07 PM org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxResolvingClassLoader$4$1 load WARNING: took 5,770ms to load/not load groovy.lang.GroovyObject$groovy$util$script15275137998231310805619$SSH_LOGIN from classLoader hudson.PluginManager$UberClassLoader 2018/05/28 05:07:798 - job/KKA/job/TRIGGER_JOB_NEW_BUILD_IN_NEXUS_FLAG/ #4533 Started by timer May 28, 2018 4:28:07 PM org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxResolvingClassLoader$4$1 load WARNING: took 6,783ms to load/not load groovy.lang.GroovyObject$groovy$util$script15275138109721310805619$SSH_LOGIN
