Could not Execute JDBC Batch Update When Inserting a Comment
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following error appears in the atlassian-fisheye*.log:
1
2
3
4
5
6
7
8
2012-09-17 22:56:36,254 WARN [btpool0-12384] util.JDBCExceptionReporter JDBCExceptionReporter-logExceptions - SQL Error: 0, SQLState: 22P05
2012-09-17 22:56:36,254 ERROR [btpool0-12384] util.JDBCExceptionReporter JDBCExceptionReporter-logExceptions - ERROR: character 0xe28093 of encoding "UTF8" has no equivalent in "LATIN1"
2012-09-17 22:56:36,255 ERROR [btpool0-12384] def.AbstractFlushingEventListener AbstractFlushingEventListener-performExecutions - Could not synchronize database state with session
org.hibernate.exception.DataException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:102)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
…
Caused by: java.sql.BatchUpdateException: Batch entry 0 insert into cru_comment (cru_create_date, cru_updated_date, cru_message, cru_draft, cru_deleted, cru_defect_raised, cru_comment_issue_key, cru_defect_approved, cru_user_id, cru_review_id, cru_reply_to_comment_id, cru_comment_id) values ('1347918996249', '1347918996249', 'testing – set to 3, suggested set to 4', '0', '0', '0', NULL, '0', '358', '244', NULL, '2431') was aborted. Call getNextException to see the cause.Cause
This situation is likely to be happening because Fisheye/Crucible currently support database encoding 'UTF-8' only.
Resolution
Convert your database encoding to 'UTF-8' as stated in this documentation.
Was this helpful?