Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
-
BEAC
Description
This should really check that the build key length on the 1. Create a new plan page will fit in to the data type used by the ORDB; instead it will allow you to complete the process only to be greeted by the Oops page. The logs show that there is a JDBC exception as the build key is longer than 255 characters:
@4000000049825760392c73a4 2009-01-29 19:26:46,959 WARN [TP-Processor60] [JDBCExceptionReporter] SQL Error: 0, SQLState: 22001 @4000000049825760392d2b3c 2009-01-29 19:26:46,959 ERROR [TP-Processor60] [JDBCExceptionReporter] ERROR: value too long for type character varying(255) @4000000049825760393243ec 2009-01-29 19:26:46,959 ERROR [TP-Processor60] [SessionImpl] Could not synchronize database state with session @40000000498257603a69933c 2009-01-29 19:26:46,959 WARN [TP-Processor60] [HibernateObjectDao] Problems getting build by key @40000000498257603a699b0c net.sf.hibernate.exception.GenericJDBCException: could not insert: [com.atlassian.bamboo.build.DefaultBuild#56524807]
But this is what the user is greeted with:
java.lang.IllegalArgumentException: object cannot be null
Internal server error - Extranet Bamboo.html
Once this happens, the user must restart their plan creation from scratch.