Build unexpected exit for some configurations

I have recenetly migrated our TeamCity server from HSQL to MySQL and everything is working ok expect a few of the build configurations do not start. Other are triggered correctly but other stop with an error "unexpected Exit" or something as it's gone before I can read it.

I looked into the teamcity logs and found the following error:

ERROR - r.serverSide.impl.BuildStarter - org.springframework.dao.DataIntegrityViolationException: ConnectionCallback; SQL []; Data truncation: Data too long for column 'BUILD_NUMBER' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'BUILD_NUMBER' at row 1
org.springframework.dao.DataIntegrityViolationException: ConnectionCallback; SQL []; Data truncation: Data too long for column 'BUILD_NUMBER' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'BUILD_NUMBER' at row 1............

I did a quick search and found the following issue which appears to give a workaround for the issue.

http://www.jetbrains.net/jira/browse/TW-1383

My questions are.
Is the workaround given in the issue accurate?
If not, please can you tell me what do I need to do to fix it?

Also, has this issue been fixed for versions following 3.1 and I should update to fix the issue properly?

Thanks in advance



Attachment(s):
error_trace.txt
6 comments
Comment actions Permalink

Hello,

The workaround is accurate, and I believe the issue should be fixed in the TeamCity 3.1.x version.

Kind regards,
KIR

0
Comment actions Permalink

thanks,

I have just realised I do not have a buildServerSpring.xml I have a buildServerSpringWeb.xml. Am I in the right place, is this just a typo on the workaround?

If so do I need to add the prop to a specific section of buildServerSpringWeb.xml?

My first guess is in mappings property list in the urlMapping bean

0
Comment actions Permalink

Hi,

What version of TC do you use? In fact, for latest versions of TeamCity you should add
connectionProperties. jdbcCompliantTruncation=false

to database.properties file

HTH,

KIR

0
Comment actions Permalink

I'm using 3.1 professinal (build 6760)

I guess that probably means I should be looking in the database config file!

0
Comment actions Permalink

I guess that probably means I should be looking in the database config file!


Correct :)

0
Comment actions Permalink

thanks, fixed the issue and now planning an upgrade :D

0

Please sign in to leave a comment.