We had a problem this morning where one of our developers (who has since been punished) committed a change to Subversion with a very long log message. TeamCity then couldn't build that project, reporting 'Unable to collect changes'.
The exception looked something like this:
[2010-01-27 09:25:15,433] INFO - r.serverSide.impl.BuildStarter - java.util.concurrent.ExecutionException: jetbrains.buildServer.vcs.VcsException: Problem collecting changes for 'MyProject :: MyProject - trunk - Testing' : Error collecting changes for VCS root 'MyProject'
org.springframework.jdbc.UncategorizedSQLException: Error executing update query with params: [15278, jblogs, I like to write very long messages...
This is more of my message...
Which goes on and on.
and on..., 1264572291635, 10, 5, 2255_2010/01/27 06:04:52 +0000, 2255, 2]; uncategorized SQLException for SQL [INSERT INTO vcs_history (MODIFICATION_ID, USER_NAME, DESCRIPTION, CHANGE_DATE, VCS_ROOT_ID, VCS_ROOT_VERSION, VERSION, DISPLAY_VERSION, CHANGES_COUNT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state ; error code ; ORA-01461: can bind a LONG value only for insert into a LONG column
; nested exception is java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
The only bug I could find which might be something to do with this was http://youtrack.jetbrains.net/issue/TW-10600
Should TeamCity be able to cope with very long log messages?
TeamCity 5.0.1, Oracle back end