• Community
  • Products
  • Bamboo
  • Questions
  • Bamboo Agent Exception : "Could not recursively kill windows process using winp; falling back to java.lang.Process#destroy"

Bamboo Agent Exception : "Could not recursively kill windows process using winp; falling back to java.lang.Process#destroy"

How can I get rid of these messages in the Bamboo Agent's log? Do I have to install something additional?

INFO   | jvm 1    | 2011/07/04 08:48:23 | 2011-07-04 08:48:23,045 ERROR [4-BAM::
BambooAgent10_2::Agent:pool-6-thread-1] [ExternalProcess] Could not recursively
kill windows process using winp; falling back to java.lang.Process#destroy
INFO | jvm 1 | 2011/07/04 08:48:23 | java.lang.NoClassDefFoundError: Could
not initialize class org.jvnet.winp.Native
INFO | jvm 1 | 2011/07/04 08:48:23 | at org.jvnet.winp.WinProcess.<in
it>(WinProcess.java:41)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.utils.process.E
xternalProcess.cancel(ExternalProcess.java:498)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.utils.process.E
xternalProcess.wrapUpProcess(ExternalProcess.java:456)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.utils.process.E
xternalProcess.finish(ExternalProcess.java:329)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.utils.process.E
xternalProcess.execute(ExternalProcess.java:373)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.process.
ProcessServiceImpl.executeProcess(ProcessServiceImpl.java:180)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.plugins.
maven.task.Maven3BuildTask.execute(Maven3BuildTask.java:75)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.task.Tas
kExecutorImpl.executeTasks(TaskExecutorImpl.java:117)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.task.Tas
kExecutorImpl.execute(TaskExecutorImpl.java:73)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.build.pi
peline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:87)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.v2.build
.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:192)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.v2.build
.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.jav
a:99)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.v2.build
.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:106)
INFO | jvm 1 | 2011/07/04 08:48:23 | at com.atlassian.bamboo.build.pi
peline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:50)
INFO | jvm 1 | 2011/07/04 08:48:23 | at java.lang.Thread.run(Thread.j
ava:662)

2 answers

1 accepted

2 votes
Accepted answer

This seems to be a known bug: https://jira.atlassian.com/browse/BAM-9003

It has been fixed in 3.1.3. If you have this version already and still experiencing the problem please update the bug report.

Nope, just updated and everything works fine. The workaround, described in BAM-9003 also worked for us until we updated to 3.1.4!

Thx a lot!

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

4,335 views 20 12
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you