[JIRA] [core] (JENKINS-30665) JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above
Title: Message Title Marcus Jacobsson assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-30665 JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above Change By: Marcus Jacobsson Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [lucene-search-plugin] (JENKINS-30234) Support "Build Display Name" Field in Lucene searches
Title: Message Title Marcus Jacobsson resolved as Fixed Verified that this works in version 3.0 Jenkins / JENKINS-30234 Support "Build Display Name" Field in Lucene searches Change By: Marcus Jacobsson Status: Open Resolved Assignee: Tobias Olsson Marcus Jacobsson Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [lucene-search-plugin] (JENKINS-30235) Wrong job links in the Lucene Search results
Title: Message Title Marcus Jacobsson resolved as Fixed I checked this and the URL is correct in version 3.0 Jenkins / JENKINS-30235 Wrong job links in the Lucene Search results Change By: Marcus Jacobsson Status: Open Resolved Assignee: Tobias Olsson Marcus Jacobsson Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [lucene-search-plugin] (JENKINS-30235) Wrong job links in the Lucene Search results
Title: Message Title Marcus Jacobsson commented on JENKINS-30235 Re: Wrong job links in the Lucene Search results This depends on where you stand where you search. We've also noticed this and I will see if we can't push in a fix when we release the support for workflow. Sometimes we also get strange search result when standing on a build and searching for a number. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [lucene-search-plugin] (JENKINS-30234) Support "Build Display Name" Field in Lucene searches
Title: Message Title Marcus Jacobsson commented on JENKINS-30234 Re: Support "Build Display Name" Field in Lucene searches Both should be searchable today. The keyword "projectname" gets its value from the builds parrents getName() and "projectdisplayname" gets the value from builds parents getDisplayname() So if for some reason the display name is not searchable today it's a bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-19) full text search
Marcus Jacobsson commented on JENKINS-19 full text search There is a plugin to improves the searh function in Jenkins https://wiki.jenkins-ci.org/display/JENKINS/Lucene-Search It only indexes data bound to the build unless you write your own extensions. 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] [workflow-plugin] (JENKINS-27458) Serialization error at end of flow not reported properly in build log, only Jenkins log
Marcus Jacobsson
commented on JENKINS-27458
Serialization error at end of flow not reported properly in build log, only Jenkins log
So as I understand it from the guide this will never work? Too bad as we kind of need to be able to do this.
import some.package.SomeClass
SomeClass a = new SomeClass("World")
node("A"){
a.setSomeValue()
echo a.greet()
}
node("B"){
a.setSomeValue()
echo a.greet()
}
a = null;
echo "This is the end"
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] [workflow-plugin] (JENKINS-27459) Not allow Jenkins to run more than one instance of the same workflow job at a time
Marcus Jacobsson created JENKINS-27459 Not allow Jenkins to run more than one instance of the same workflow job at a time Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 17/Mar/15 9:20 AM Description: Right now Jenkins can start unlimited number of parallel instances of the same workflow job. We would like to be able to block so only one instance of for example DEV-workflow-plugin can run at a same time. If another is started then it should be queued just like normal builds are. Environment: Workflow 1.4 Jenkins 1.596.1 Project: Jenkins Priority: Major Reporter: Marcus Jacobsson 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] [workflow-plugin] (JENKINS-27458) Build fail when declaring a class
Marcus Jacobsson
created JENKINS-27458
Build fail when declaring a class
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
17/Mar/15 9:15 AM
Description:
We start by creating a class in the groovy script but we've also tried having another groovy script as well as create the class in Java.
When we then declare create an object with the class "def sc = new SimpleClass("Nisse")" the workflow will exit with an error code.
The part "echo "this is the end"" will not be executed.
If I remove the def sc = new ... then the job will exit and all the echo commands will run.
workflow.groovy
class SimpleClass{
def name = ""
public SimpleClass(def name){
this.name = name
}
public def greet(){
return "Hello " + this.name
}
}
def sc = new SimpleClass("Nisse")
echo sc.greet()
node("linux || windows") {
echo "enter node"
ws("rb-sb-revision") {
echo "Node + WS 1"
}
echo "exit WS"
}
echo "this is the end"
Environment:
Jenkins 1.596.1
Workflow plugin 1.4
Xubuntu 14.04
Groovy Version: 1.8.6 JVM: 1.7.0_76 Vendor: Oracle Corporation OS: Linux
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Project:
Jenkins
Priority:
Critical
Reporter:
Marcus Jacobsson
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] [workflow-plugin] (JENKINS-26860) restrict parallel runs
Marcus Jacobsson commented on JENKINS-26860 restrict parallel runs I tried using stage like this echo "ccc" stage concurrency: 1, name: 'test' echo "a" sleep 50 echo "b" That results in a build list like this Failed Console Output #222 Mar 17, 2015 12:42:59 PM Not built Console Output #221 Mar 17, 2015 12:42:58 PM Not built Console Output #220 Mar 17, 2015 12:42:57 PM Not built Console Output #219 Mar 17, 2015 12:42:56 PM Not built Console Output #218 Mar 17, 2015 12:42:55 PM Failed Console Output #217 Mar 17, 2015 12:42:54 PM It would be more desirable to not get the Not built each time someone triggers a new build. Sure I can see a point to allow multiple runs at the same time in some cases but in our case it would not really be such a good idea for us, at least not right now. That is why we would like to prevent another build from running if one is already running. I can live with having two builds running where the last one is waiting for the first one to complete. But getting a Not built each time someone triggers or if a plugin triggers looks a bit messy to me. 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] [workflow-plugin] (JENKINS-27458) Build fail when declaring a class
Marcus Jacobsson updated JENKINS-27458 Build fail when declaring a class Change By: Marcus Jacobsson (17/Mar/15 11:34 AM) Environment: Jenkins1.596.1Workflowplugin1.4Xubuntu14.04 GroovyVersion:1.8.6JVM:1.7.0_76Vendor:OracleCorporationOS:Linux Java(TM)SERuntimeEnvironment(build1.7.0_76-b13) 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] [workflow-plugin] (JENKINS-27458) Build fail when declaring a class
Marcus Jacobsson
commented on JENKINS-27458
Build fail when declaring a class
If I on the other hand write like this the job will complete and the build will be green
echo sc.greet()
node("linux || windows") {
echo "enter node"
ws("rb-sb-revision") {
def sc = new SimpleClass("Nisse")
echo "Node + WS 1"
}
echo "exit WS"
}
echo "this is the end"
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] [workflow-plugin] (JENKINS-24673) SimpleBuildWrapper
Marcus Jacobsson commented on JENKINS-24673 SimpleBuildWrapper Was looking a bit more on this now that I got some free time again, the only thing we need right now is to be able to create a wrapper for the listener output. So we can filter the output and color code the output. For example we have a plugin that formats or output simular to https://wiki.jenkins-ci.org/display/JENKINS/Timestamper and https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin as well as a plugin to filer out passwords from the console. 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-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Marcus Jacobsson commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Have the same problem with Jenkins LTS 1.580.3. In our case the nodes goes offline a few hours after restarting the master server and it's not all node, just a few each time (different nodes each time). The server is running on Ubuntu 14.04 and the slaves are running Windows 7 x64 Connection was broken java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:616) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 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) 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] [workflow] (JENKINS-24672) GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux
Marcus Jacobsson created JENKINS-24672 GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow Created: 11/Sep/14 1:05 PM Description: I don't know if it could be something with the os version is taken from the master instead of the node and thus trying to run a .exe file on a Linux server. Console output Running on WSAB101036 (10.158.238.104) in /home/ci/ci-build/workspace/My-First-Workflow Running: Allocate node : Body : Start Running: Git Cloning the remote Git repository Cloning repository https://github.com/jenkinsci/lucene-search-plugin.git git.exe init /home/ci/ci-build/workspace/My-First-Workflow # timeout=10 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Could not init /home/ci/ci-build/workspace/My-First-Workflow at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:485) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:388) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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) Caused by: hudson.plugins.git.GitException: Error performing command: git.exe init /home/ci/ci-build/workspace/My-First-Workflow at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1414) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1383) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1093) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:483) ... 11 more Caused by: java.io.IOException: Cannot run program "git.exe" (in directory "/home/ci/ci-build/workspace/My-First-Workflow"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:802) at hudson.Launcher$ProcStarter.start(Launcher.java:380) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1403) ... 15 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.init(UNIXProcess.java:186) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) ... 20 more Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow java.lang.RuntimeException: hudson.AbortException at org.jenkinsci.plugins.workflow.cps.CpsStepContext.replay(CpsStepContext.java:388) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:156) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:79) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at Script1.run(Script1.groovy:2) at Unknown.Unknown(Unknown) at __cps.transform__(Native Method) at
[JIRA] [workflow] (JENKINS-24673) Build wrappers in Workflow plugin
Marcus Jacobsson created JENKINS-24673 Build wrappers in Workflow plugin Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: workflow Created: 11/Sep/14 1:08 PM Description: This may be something that I've missed but how are you planing on adding support to add build wrappers to the Workflow plugin. We depend a lot on a few plugins to modify the console output to for example color code, find match patterns and to filter out password. Project: Jenkins Priority: Major Reporter: Marcus Jacobsson 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] [ansicolor] (JENKINS-18502) consoloe output stacktrace
Marcus Jacobsson created JENKINS-18502 consoloe output stacktrace Issue Type: Bug Assignee: Unassigned Components: ansicolor Created: 26/Jun/13 6:28 AM Description: When I click on Full log I get the following stacktrace. Works on some builds but not all. Status Code: 500 Exception: java.lang.IndexOutOfBoundsException Stacktrace: javax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at filters.SBOIcons.doFilter(SBOIcons.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
[JIRA] [ansicolor] (JENKINS-18502) console output stacktrace
Marcus Jacobsson updated JENKINS-18502 console output stacktrace Change By: Marcus Jacobsson (26/Jun/13 6:29 AM) Summary: consoloe console outputstacktrace Environment: Jenkins1.509.1 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/groups/opt_out.
[JIRA] [ansicolor] (JENKINS-18502) console output stacktrace
Marcus Jacobsson
updated JENKINS-18502
console output stacktrace
Change By:
Marcus Jacobsson
(26/Jun/13 6:32 AM)
Priority:
Blocker
Major
Description:
WhenIclickonFulllogIgetthefollowingstacktrace.Worksonsomebuildsbutnotall.
ItlookslikeitoccurswhentorunningtwodifferentBuildWrappersthatmodifiestheprogramoutput.
{code}StatusCode:500Exception:java.lang.IndexOutOfBoundsExceptionStacktrace:javax.servlet.ServletException:java.lang.IndexOutOfBoundsException atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:770) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:583) atorg.kohsuke.stapler.Stapler.service(Stapler.java:214) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:722) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) atfilters.SBOIcons.doFilter(SBOIcons.java:39) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson commented on JENKINS-18169 Deadlock when running multiple delete I noticed that this is probably the same as https://issues.jenkins-ci.org/browse/JENKINS-18199 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson updated JENKINS-18169 Deadlock when running multiple delete stack trace shown in Javamelody when deleting logs from two builds in prallel Change By: Marcus Jacobsson (14/Jun/13 6:29 AM) Attachment: build1.txt 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson updated JENKINS-18169 Deadlock when running multiple delete stack trace shown in Javamelody when deleting logs from two builds in prallel Change By: Marcus Jacobsson (14/Jun/13 6:28 AM) Attachment: build2.txt 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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson resolved JENKINS-18011 as Not A Defect Deadlock issue remote slaves Change By: Marcus Jacobsson (05/Jun/13 2:41 PM) Status: Open Resolved Resolution: NotADefect 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson
created JENKINS-18169
Deadlock when running multiple delete
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
03/Jun/13 6:58 AM
Description:
Tried to remove ~20 builds in parallel with 30 days of build logs (a lot of files) and this resulted in a deadlock and we needed to restart the server.
JavaMelody listed the doDelete threads as deadlocked and showed
1 x hudson.model.Job.delete(Job.java:587)
17 x hudson.model.Project.getPublishersList(Project.java:114)
as a result of the deadlock we can't edit builds anymore
/configSubmit : http-bio-8080-exec-3552 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3503 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3543 yes 5 BLOCKED hudson.model.Job.delete(Job.java:587)
Looking in project.java it looks like a deprecated method is used
/**
* @deprecated as of 1.463 We will be soon removing the restriction that
* only one instance of publisher is allowed per type. Use
* {@link #getPublishersList()} instead.
*/
public MapDescriptorPublisher,Publisher getPublishers() {
return publishers.toMap();
}
Environment:
Jenkins 1.509.1 running on Ubuntu 12.04 with JDK 1.7
Project:
Jenkins
Priority:
Major
Reporter:
Marcus Jacobsson
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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson updated JENKINS-18011 Deadlock issue remote slaves Change By: Marcus Jacobsson (22/May/13 11:43 AM) Priority: Major Critical 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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson
updated JENKINS-18011
Deadlock issue remote slaves
Change By:
Marcus Jacobsson
(21/May/13 10:50 AM)
Description:
JenkinsslavesrunningonWindowshaveatendencytodeadlockwhenprogramsaresendingalotofdatasimultaneously.ReadingthethreaddumpfromVisualVMwecanseethatproc.javatriestowritetodeadlockstreamresultinginhangingbuildsStringmsg=Processleakedfiledescriptors.Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+buildformoreinformation;Throwablee=newException().fillInStackTrace();LOGGER.log(Level.WARNING,msg,e);
{code}
pool-1-thread-833-Threadt@1926010java.lang.Thread.State:BLOCKED atjava.util.logging.StreamHandler.publish(UnknownSource) -waitingtolock1502546(ajava.util.logging.ConsoleHandler)ownedbypool-1-thread-927t@1926604 atjava.util.logging.ConsoleHandler.publish(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) atjava.util.logging.Logger.doLog(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) athudson.Proc$LocalProc.join(Proc.java:330) athudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) atsun.reflect.GeneratedMethodAccessor127.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:58) atjava.lang.Thread.run(UnknownSource)
{code}
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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson
updated JENKINS-18011
Deadlock issue remote slaves
Change By:
Marcus Jacobsson
(21/May/13 10:51 AM)
Description:
JenkinsslavesrunningonWindowshaveatendencytodeadlockwhenprogramsaresendingalotofdatasimultaneously.ReadingthethreaddumpfromVisualVMwecanseethatproc.javatriestowritetodeadlockstreamresultinginhangingbuilds
{code}
Stringmsg=Processleakedfiledescriptors.Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+buildformoreinformation;Throwablee=newException().fillInStackTrace();LOGGER.log(Level.WARNING,msg,e);
{code}
{code}pool-1-thread-833-Threadt@1926010java.lang.Thread.State:BLOCKED atjava.util.logging.StreamHandler.publish(UnknownSource) -waitingtolock1502546(ajava.util.logging.ConsoleHandler)ownedbypool-1-thread-927t@1926604 atjava.util.logging.ConsoleHandler.publish(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) atjava.util.logging.Logger.doLog(UnknownSource) atjava.util.logging.Logger.log(UnknownSource) athudson.Proc$LocalProc.join(Proc.java:330) athudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) atsun.reflect.GeneratedMethodAccessor127.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) athudson.remoting.Engine$1$1.run(Engine.java:58) atjava.lang.Thread.run(UnknownSource){code}
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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson edited a comment on JENKINS-18011 Deadlock issue remote slaves Full thread dump Java HotSpot(TM) Client VM (23.7-b01 mixed mode): "RMI TCP Connection(7)-10.158.226.24" - Thread t@1933099 java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) - locked 9adbe1 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - locked 1647392 (a java.util.concurrent.ThreadPoolExecutor$Worker) "pool-1-thread-1016" - Thread t@1933098 java.lang.Thread.State: TIMED_WAITING at sun.misc.Unsafe.park(Native Method) - parking to wait for 9aa718 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(Unknown Source) at java.util.concurrent.SynchronousQueue.poll(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - None "RMI TCP Connection(6)-10.158.226.24" - Thread t@1933097 java.lang.Thread.State: RUNNABLE at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImpl.dumpAllThreads(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) at javax.management.StandardMBean.invoke(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$300(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: - locked 7d7a7c (a
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson created JENKINS-18011 Deadlock issue remote slaves Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/May/13 12:03 PM Description: Jenkins slaves running on Windows have a tendency to deadlock when programs are sending a lot of data simultaneously. Reading the threaddump from VisualVM we can see that proc.java tries to write to deadlock stream resulting in hanging builds """ String msg = "Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information"; Throwable e = new Exception().fillInStackTrace(); LOGGER.log(Level.WARNING,msg,e); """ "pool-1-thread-833" - Thread t@1926010 java.lang.Thread.State: BLOCKED at java.util.logging.StreamHandler.publish(Unknown Source) waiting to lock 1502546 (a java.util.logging.ConsoleHandler) owned by "pool-1-thread-927" t@1926604 at java.util.logging.ConsoleHandler.publish(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at java.util.logging.Logger.doLog(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:330) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Environment: Linux Master runing programs on Windows slaves Verified in Jenkins 1.480.1 and Jenkins 1.509.1 Project: Jenkins Labels: slave Priority: Major Reporter: Marcus Jacobsson 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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson commented on JENKINS-18011 Deadlock issue remote slaves Related to https://github.com/jenkinsci/jenkins/pull/665 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/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson commented on JENKINS-18011 Deadlock issue remote slaves 2013-05-20 13:54:07 Full thread dump Java HotSpot(TM) Client VM (23.7-b01 mixed mode): "RMI TCP Connection(7)-10.158.226.24" - Thread t@1933099 java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) locked 9adbe1 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: locked 1647392 (a java.util.concurrent.ThreadPoolExecutor$Worker) "pool-1-thread-1016" - Thread t@1933098 java.lang.Thread.State: TIMED_WAITING at sun.misc.Unsafe.park(Native Method) parking to wait for 9aa718 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(Unknown Source) at java.util.concurrent.SynchronousQueue.poll(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: None "RMI TCP Connection(6)-10.158.226.24" - Thread t@1933097 java.lang.Thread.State: RUNNABLE at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImpl.dumpAllThreads(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) at javax.management.StandardMBean.invoke(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$300(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers:
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson edited a comment on JENKINS-18011 Deadlock issue remote slaves Related to https://github.com/jenkinsci/jenkins/pull/782 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/groups/opt_out.
[JIRA] [core] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading dashboard
Marcus Jacobsson commented on JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard We are also having some problem with long load times after upgrading to a version with lazy loading. We are using getPreviousSuccessfulBuild quite frequently and we will disable the code that uses this operation and see if it helps. We have are running a Jenkins server with close to 1000 different jobs and noticed that we have a lot of hits on the root, that I think will list all builds. After looking at some statistics from JavaMelody we see that we have quite a lot of hits to the root and to cc.xml in the root. Could this force Jenkins to load unnecessary build data to the memory? And if so, is there a way to prevent this? Request, % of cumulative time, Hits, Mean time (ms) /cc.xml GET 11 79,903 21 / GET 6 127 7,746 101,459 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/groups/opt_out.
[JIRA] [master-slave] (JENKINS-13330) Jenkins slave hangs in post build phase
Marcus Jacobsson commented on JENKINS-13330 Jenkins slave hangs in post build phase This could be related to the problem we have with hanging slaves. The problem we had was that Jenkins noticed that the program it is running has ended and thus thinks that the program has a bug where it won't send the eof tag. Due to this it wants to write back a message about a wiki post. ""String msg = "Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information"; Throwable e = new Exception().fillInStackTrace(); LOGGER.log(Level.WARNING,msg,e);"" But at this point the logger connection is deadlocked and the job will hang. To prevent the hanging we've patched our version of Jenkins with https://github.com/jenkinsci/jenkins/pull/665. 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/groups/opt_out.
[JIRA] (JENKINS-17174) Javascript proxy failes when sending html/xml formated messages
Marcus Jacobsson updated JENKINS-17174 _javascript_ proxy failes when sending html/xml formated messages Change By: Marcus Jacobsson (12/Mar/13 1:10 PM) Environment: Jenkins1.480.3 testedonUbuntu12.04andWindows7bothusingdebuginginmavenandtomcat 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/groups/opt_out.
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Marcus Jacobsson commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 We've started to receive this error after updating to jdk-7u9-windows-x64. The problem is that the nunit constantly fails on when trying to clean. We are currently running a patched version of 1.480.1 Recording NUnit tests results 16:57:17 - ERROR: Publisher hudson.plugins.nunit.NUnitPublisher aborted due to exception 16:57:17 - hudson.util.IOException2: remote file operation failed: *\temporary-junit-reports at hudson.remoting.Channel@271d097d:WSAB101036 16:57:17 - at hudson.FilePath.act(FilePath.java:838) 16:57:17 - at hudson.FilePath.act(FilePath.java:824) 16:57:17 - at hudson.FilePath.deleteRecursive(FilePath.java:908) 16:57:17 - at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:115) 16:57:17 - at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) 16:57:17 - at hudson.model.Build$BuildExecution.post2(Build.java:183) 16:57:17 - at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) 16:57:17 - at hudson.model.Run.execute(Run.java:1527) 16:57:17 - at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:57:17 - at hudson.model.ResourceController.execute(ResourceController.java:88) 16:57:17 - at hudson.model.Executor.run(Executor.java:236) 16:57:17 - Caused by: java.io.IOException: Remote call on * failed 16:57:17 - at hudson.remoting.Channel.call(Channel.java:673) 16:57:17 - at hudson.FilePath.act(FilePath.java:831) 16:57:17 - ... 12 more 16:57:17 - Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.util.jna.Kernel32 16:57:17 - at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:62) 16:57:17 - at hudson.Util.isSymlink(Util.java:314) 16:57:17 - at hudson.Util.deleteRecursive(Util.java:279) 16:57:17 - at hudson.FilePath$11.invoke(FilePath.java:910) 16:57:17 - at hudson.FilePath$11.invoke(FilePath.java:908) 16:57:17 - at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2236) 16:57:17 - at hudson.remoting.UserRequest.perform(UserRequest.java:118) 16:57:17 - at hudson.remoting.UserRequest.perform(UserRequest.java:48) 16:57:17 - at hudson.remoting.Request$2.run(Request.java:326) 16:57:17 - at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 16:57:17 - at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 16:57:17 - at java.util.concurrent.FutureTask.run(Unknown Source) 16:57:17 - at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 16:57:17 - at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 16:57:17 - at hudson.remoting.Engine$1$1.run(Engine.java:60) 16:57:17 - at java.lang.Thread.run(Unknown Source) 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
