|Can't really kill a job [message #1389209]
||Fri, 27 June 2014 13:44
| Fabrizio Giudici
Registered: May 2013
a customer of mine would like to use Hudson to start/stop a simple application used for testing. The application generates some random traffic to exercise a webapp under test. It is basically a main() which sets up some java.util.Timer's. The application is normally launched from the command line and runs forever, until it is stopped with Ctrl^C.
We configured a Hudson job to run it, with the idea that pressing the red stop button would quit the test. But this just doesn't happen. The application is run by means of Maven exec plugin. I first tried exec:java, then exec:exec, to be sure that a new JVM is spawned independently of Maven. But the end result doesn't change: Hudson declares that the job is stopped, but I can still see it running in the list of active processes, and it needs to be manually killed. I frankly don't understand what's happening... We even installed a shutdownhook to explicitly kill the timers (even though I wouldn't understand why this is needed), but the hook is never called.
The thing happens on Windows 2008 R2, JDK 1.7.0_45. Maven is launched by means of the embedded support in Hudson.
[Updated on: Fri, 27 June 2014 13:45]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03604 seconds