| << Back to previous view |
|
[QB-2914] QB raises PostgreSQL errors during writing into audit log table
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 7.0.6 |
| Fix Version/s: | 7.0.7 |
| Type: | Bug | Priority: | Minor |
| Reporter: | AlSt | Assigned To: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
QB seems to write a very long audit log somewhere and so it is failing. Maybe the data type for the table column is to tight or the audit log string is too long.
LOG: 2017-03-03 11:49:54 CET [139790-1] quickbuild-stg@quickbuild-stg ERROR: value too long for type character varying(255) 2017-03-03 11:49:54 CET [139790-2] quickbuild-stg@quickbuild-stg STATEMENT: / insert com.pmease.quickbuild.model.Audit / insert into QB_AUDIT (QB_ACTION, QB_CONTENT, QB_PREVIOUS_CONTENT, QB_SOURCE, QB_TIMESTAMP, QB_USER, QB_ID) values ($1, $2, $3, $4, $5, $6, $7) Also the QB server log shows a lot of these: 2017-03-03 11:49:40,016 [pool-1-thread-1676] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,016 [pool-1-thread-1676] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,042 [pool-1-thread-1685] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,043 [pool-1-thread-1685] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,063 [pool-1-thread-1690] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,064 [pool-1-thread-1690] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,080 [pool-1-thread-1724] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,081 [pool-1-thread-1724] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,155 [pool-1-thread-1764] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,156 [pool-1-thread-1764] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,181 [pool-1-thread-1824] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,181 [pool-1-thread-1824] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,181 [pool-1-thread-1830] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,182 [pool-1-thread-1830] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,195 [pool-1-thread-1880] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,196 [pool-1-thread-1880] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,201 [pool-1-thread-1918] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,202 [pool-1-thread-1918] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) 2017-03-03 11:49:40,202 [pool-1-thread-1893] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 22001 2017-03-03 11:49:40,202 [pool-1-thread-1893] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: value too long for type character varying(255) |
| Comments |
| Comment by Robin Shen [ 09/Mar/17 07:35 AM ] |
| Increasing size of source field has side effects on other databases. For instance, MySQL then creates the field as BLOB text, and is not able to be queried. This may also happens for Oracle. The workaround is to make configuration hierarchy less deeper to avoid too long path name |