Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to kill runaway job (due to java.lang.NullPointerException)

We had a job running when during that time the MySQL server went away (and restarted soon after) but this resulted in a runaway job which when trying to 'stop' it, resulted in the NPE:


Version: 6.10.4
Build: 61009
Build Date: 21 Nov 2019

Request information:

  • Request URL: http://<our url>:8085/build/admin/stopPlan.action
  • Port: 8085
  • URI: /build/admin/stopPlan.action
  • Context path:
  • Servlet path: /build/admin/stopPlan.action
  • Path info:
  • Query string: planResultKey=KMT-DEPLOY-16493&returnUrl=%2Fbrowse%2FKMT-DEPLOY-16493

Stack Trace: is too big, thus linked here


So how to we kill the running job now without restarting bamboo entirely? 

1 answer

1 accepted

1 vote
Answer accepted
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 24, 2020 • edited

What you observe is most probably the data integrity issue caused by MySQL outage. The build cannot be stopped because there's nothing that should be in fact stopped.

IMO restarting Bamboo Server is the best course of action.

Thanks, seems like the best way to go indeed.


After restarting bamboo itself, everything was back to normal. The weird thing is though that before restarting bamboo the other pages still kept working (or atleast seemed to have recovered)


Ow well, let's just chalk this up to a mysql outage and just restart bamboo

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events