Bamboo deployments failing with GenericJDBCException: could not execute batch Edited


Today our deployments started failing with the error:

JDBC exception on Hibernate data access: SQLException for SQL [insert into DEPLOYMENT_RESULT (VERSION_ID, VERSION_NAME, ENVIRONMENT_ID, DEPLOYMENT_STATE, LIFE_CYCLE_STATE, STARTED_DATE, QUEUED_DATE, EXECUTED_DATE, FINISHED_DATE, AGENT_ID, VARIABLE_CONTEXT_BASELINE_ID, TRIGGER_REASON, DEPLOYMENT_RESULT_ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [null]; error code [0]; could not execute batch; nested exception is org.hibernate.exception.GenericJDBCException: could not execute batch

This pops up during the deployment preview and the deployment cannot continue.

Please forgive me as I'm not super familiar with Bamboo. I saw another question with a similar title, but a different error.


Here's my config.xml with the license details removed:

<?xml version="1.0" encoding="UTF-8"?>
<property name="">${bambooHome}\artifacts</property>
<property name="">${bambooHome}\xml-data\configuration</property>
<property name="">failover:(tcp://;maxReconnectAttempts=10</property>
<property name="">nio://</property>
<property name="">${bambooHome}\xml-data\builds</property>
<property name="">${bambooHome}\xml-data\repository-specs</property>
<property name="buildWorkingDir">${bambooHome}\xml-data\build-dir</property>
<property name="daily.backup.dir">${bambooHome}\backups</property>
<property name="hibernate.c3p0.acquire_increment">3</property>
<property name="hibernate.c3p0.idle_test_period">30</property>
<property name="hibernate.c3p0.max_size">100</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.min_size">3</property>
<property name="hibernate.c3p0.timeout">120</property>
<property name="hibernate.connection.driver_class">org.hsqldb.jdbcDriver</property>
<property name="hibernate.connection.password"></property>
<property name="hibernate.connection.url">jdbc:hsqldb:${bambooHome}/database/defaultdb</property>
<property name="hibernate.connection.username">sa</property>
<property name="hibernate.dialect">com.atlassian.bamboo.hibernate.HSQL18Dialect</property>
<property name="hibernate.setup">true</property>
<property name="license.string">our_license_string</property>
<property name="lucene.index.dir">${bambooHome}\index</property>
<property name="serverId">our_server_id</property>
<property name="serverKey">server_key</property>
<property name="webwork.multipart.saveDir">${bambooHome}\temp</property>


1 answer

1 vote

Hello @Joshua Gribbon,

Please, notice it is recommended using MySQL, PostgreSQL, Microsoft SQL Server or Oracle DB in production instances instead of HSQLDB.

In relation to the error you are experiencing, you could:

  • raise a support case where more information can be provided OR
  • enable SQL debug logging in Bamboo (<bamboo-install>/atlassian-bamboo/WEB-INF/classes/ by uncomment:
    ## log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true')
    ## log hibernate prepared statement parameter values
    • restart Bamboo
    • replicate the issue as new entries to the logs (<bamboo-install>/logs/catalina.out) will be generated
    • review the INSERT statement that is failing, checking the null mentioned in error

NOTE: A considerable amount of logging will be generated, having a direct impact on filesystem disk space.

Kind regards,


Hey Rafael, thanks for the speedy response! 

I've been trying to avoid switching databases but I guess the time of reckoning is upon me. I'll switch to SQL Server and then update here.

We decided to just make the switch to Pipelines. We were considering this anyway so this was the sign.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,815 views 0 6
Read article

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