Build plan fails with NullPointerException

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.


The following error is presented when attempting to run a build through the Run > Run plan button in Bamboo:

Site homepage
A system error has occurred - our apologies!

Version: 5.10.3
Build: 51020
Build Date: 14 Mar 2016
Request information:
Request URL: https://webserver.bamboo/builds/build/admin/triggerManualBuild.action
Scheme: https
Server: webserver.bamboo
Port: 443
URI: /builds/build/admin/triggerManualBuild.action
Context path: /builds
Servlet path: /build/admin/triggerManualBuild.action
Path info:
Query string: buildKey=GIT-BIT&buildKey=GIT-BIT
Stack Trace:
    at com.atlassian.bamboo.plan.TriggerableInternalKeyImpl.<init>(
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.startManualBuild(
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.start(
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$
    at com.atlassian.bamboo.util.CacheAwareness.withValuesOlderThanTimestampReloaded(
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.startManualExecution(
    at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.startManualExecution(
    at com.atlassian.bamboo.plan.DelegatingPlanExecutionManager.startManualExecution(
    at com.atlassian.bamboo.ww2.BambooActionSupport.execute(
    at sun.reflect.GeneratedMethodAccessor2770.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(



  • Bamboo using Netflix Zuul as the proxy implementation.

Diagnostic Steps

  • At the end of the request we can see that the buildKey parameter is showing up twice. This is also observed from the Query String information in the stack trace above. This causes the entire triggerManualBuild request to look like this:



Zuul pulls the Query String from the URL and from the body and joins them, thus creating duplicate parameters:


This problem has been fixed in version 1.1.4 of Spring Cloud Netflix.

Upgrade to resolve the issue.

Last modified on Jul 20, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.