[JIRA] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.

2014-12-16 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-26087


Jobs sitting on the queue waiting for next available executor.















Workaround: Use a JRE that doesn't suck as badly as J9.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.

2014-12-16 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-26087


Jobs sitting on the queue waiting for next available executor.
















Change By:


Daniel Beck
(16/Dec/14 10:11 PM)




Labels:


java-ibm



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.

2014-12-16 Thread jllo...@us.ibm.com (JIRA)














































jose lopez
 commented on  JENKINS-26087


Jobs sitting on the queue waiting for next available executor.















Forgot to add that if I restart Jenkins jobs seem to be going to the master and getting executed but after a while (2 or 3 jobs down the road) they start going back to the queue and not moving.

This happens when I execute the jobs manually or triggered automatically by another job (pipeline)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.

2014-12-16 Thread jllo...@us.ibm.com (JIRA)














































jose lopez
 created  JENKINS-26087


Jobs sitting on the queue waiting for next available executor.















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


16/Dec/14 4:08 PM



Description:


Jobs get stuck in the queue even if we have plenty of executors available.
Jobs are supposed to go straight to the master node which i have set to "utilize this node as much as possible" but still no luck.

This is what I see in the logs:

Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info

Started SelectChannelConnector@0.0.0.0:8080

Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info

Started Ajp13SocketConnector@0.0.0.0:8009

Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info

AJP13 is not a secure protocol. Please protect port 8009

Dec 16, 2014 10:05:15 AM INFO winstone.Logger logInternal

Winstone Servlet Engine v2.0 running: controlPort=disabled

Dec 16, 2014 10:05:15 AM INFO jenkins.InitReactorRunner$1 onAttained

Started initialization

Dec 16, 2014 10:05:16 AM INFO hudson.ClassicPluginStrategy createPluginWrapper

Plugin build-pipeline-plugin.jpi is disabled

Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate

Ignoring /var/lib/jenkins/plugins/build-name-setter.hpi because /var/lib/jenkins/plugins/build-name-setter.jpi is already loaded

Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate

Ignoring /var/lib/jenkins/plugins/rtc.hpi because /var/lib/jenkins/plugins/rtc.jpi is already loaded

Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate

Ignoring /var/lib/jenkins/plugins/copy-to-slave.hpi because /var/lib/jenkins/plugins/copy-to-slave.jpi is already loaded

Dec 16, 2014 10:05:16 AM INFO jenkins.InitReactorRunner$1 onAttained

Listed all plugins

Dec 16, 2014 10:05:16 AM INFO hudson.plugins.greenballs.PluginImpl start

Green Balls!

Dec 16, 2014 10:05:16 AM INFO jenkins.InitReactorRunner$1 onAttained

Prepared all plugins

Dec 16, 2014 10:05:18 AM INFO jenkins.InitReactorRunner$1 onAttained

Started all plugins

Dec 16, 2014 10:05:18 AM INFO jenkins.InitReactorRunner$1 onAttained

Augmented all extensions

Dec 16, 2014 10:05:19 AM INFO jenkins.InitReactorRunner$1 onAttained

Loaded all jobs

Dec 16, 2014 10:05:20 AM INFO org.jenkinsci.main.modules.sshd.SSHD start

Started SSHD at port 60003

Dec 16, 2014 10:05:20 AM INFO jenkins.InitReactorRunner$1 onAttained

Completed initialization

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave1

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave2

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave3

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave4

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave5

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave6

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave7

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave8

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave9

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave10

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave11

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave12

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave13

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave14

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect

Attempting to reconnect AutoSlave15

Dec 16, 2014 10:05:20 AM INFO hudson.slaves.S