java.lang.Exception

Jenkins JIRA | Stefan Waigand | 4 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Hello, the process tree killer seems to fail on windows 7 while it works on a windows xp. I install todays Jenkins ver. 1.527, add a node which runs windows 7, add a new job that runs the batch command "start calc" (which creates a spawned process) and tie it to this node. The node connects to the master with java -jar slave.jar -jnlpUrl http://10.216.47.91:8080/computer/win7/slave-agent.jnlp When i start the job the console output shows: d:\temp\workspace\1>start calc d:\temp\workspace\1>exit 0 Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Finished: SUCCESS so far, so good On the slave, the calculator opens and stays open. The console running slave.jar says: Aug 14, 2013 5:22:56 PM hudson.Proc$LocalProc join WARNING: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:329) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1003) 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 hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) 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:63) at java.lang.Thread.run(Unknown Source) This happens independently if i run java in a cmd.exe with or without admin privileges. If i execute the job on the master, the same happens. When i look into the process list with process explorer, the calc.exe has the BUILD_ID set. Can somebody reproduce this? Shouldn't the process tree killer find and terminate this process? Thanks!

    Jenkins JIRA | 4 years ago | Stefan Waigand
    java.lang.Exception
  2. 0

    Hello, the process tree killer seems to fail on windows 7 while it works on a windows xp. I install todays Jenkins ver. 1.527, add a node which runs windows 7, add a new job that runs the batch command "start calc" (which creates a spawned process) and tie it to this node. The node connects to the master with java -jar slave.jar -jnlpUrl http://10.216.47.91:8080/computer/win7/slave-agent.jnlp When i start the job the console output shows: d:\temp\workspace\1>start calc d:\temp\workspace\1>exit 0 Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Finished: SUCCESS so far, so good On the slave, the calculator opens and stays open. The console running slave.jar says: Aug 14, 2013 5:22:56 PM hudson.Proc$LocalProc join WARNING: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:329) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1003) 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 hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) 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:63) at java.lang.Thread.run(Unknown Source) This happens independently if i run java in a cmd.exe with or without admin privileges. If i execute the job on the master, the same happens. When i look into the process list with process explorer, the calc.exe has the BUILD_ID set. Can somebody reproduce this? Shouldn't the process tree killer find and terminate this process? Thanks!

    Jenkins JIRA | 4 years ago | Stefan Waigand
    java.lang.Exception
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    Exception shown at windows slave console during restart of tomcat

    Google Groups | 5 years ago | Varghese Renny
    java.lang.Exception

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.Exception

      No message provided

      at hudson.Proc$LocalProc.join()
    2. Hudson
      Launcher$RemoteLaunchCallable$1.join
      1. hudson.Proc$LocalProc.join(Proc.java:329)
      2. hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1003)
      2 frames
    3. Java RT
      Method.invoke
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      2. sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      3. sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      4. java.lang.reflect.Method.invoke(Unknown Source)
      4 frames
    4. Hudson :: Remoting Layer
      InterceptingExecutorService$1.call
      1. hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
      2. hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
      3. hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
      4. hudson.remoting.UserRequest.perform(UserRequest.java:118)
      5. hudson.remoting.UserRequest.perform(UserRequest.java:48)
      6. hudson.remoting.Request$2.run(Request.java:326)
      7. hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      7 frames
    5. Java RT
      ThreadPoolExecutor$Worker.run
      1. java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
      2. java.util.concurrent.FutureTask.run(Unknown Source)
      3. java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      4 frames
    6. Hudson :: Remoting Layer
      Engine$1$1.run
      1. hudson.remoting.Engine$1$1.run(Engine.java:63)
      1 frame
    7. Java RT
      Thread.run
      1. java.lang.Thread.run(Unknown Source)
      1 frame