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

Bamboo deployments failing with GenericJDBCException: could not execute batch



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
rsperafico Atlassian Team Jan 02, 2018

Hello @Josh,

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

Atlassian Community Events