Very long VCS log messages causing exceptions
Hi,
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 [72000]; error code [1461]; 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?
Thanks,
Andy
TeamCity 5.0.1, Oracle back end
Please sign in to leave a comment.
Hello Andy,
Which version of Oracle JDBC driver are you using?
If less than 10.1.0.4 could you please upgrade the JDBC driver up to 10.1.0.4 or newer?
Regards,
KIR
We're using 10.2.0.1.0
Thanks,
Andy
Hello Andy,
The problem is described at http://forums.oracle.com/forums/thread.jspa?messageID=3929559
Please add the following option to database.properties file:
Hope this helps,
KIR
Thanks, Kirill, I'll add the setting and monitor for any repeat eposides.
Andy
Hi,
I've just encountered this problem in Team City 7.0.2 (build 21349), running JRE 1.7.0-b147, and Oracle JDBC driver 11.2.0.2.0 on Linux.
I'm not very familiar with the Team City configuration files, but I couldn't find a database.properties, so I couldn't use the fix you suggest.
In the end, I fixed the problem by modifying the commit message, for reference:
However, it would be good to know how to fix this in Team City (or even better, for it to just work out of the box).
Thanks,
Mark