Home → Bug Reports →

Max_allowed_packet error

Admin Functions

• Remove

Travis F.

09 Jan, 2012 10:13 PM

I have a user attempting to upload a ~37mb zip file. The global max upload is set to 40mb (40480kb to be precise) so I feel there shouldn't be a problem and yet when creating the file asset of the zip file I get:

`An error occurred during editing: Hibernate flushing: Could not execute JDBC batch update; SQL [update cxml_blob set data=? where id=?]; Packet for query is too large (37183979 > 16777216). You can change this value on the server by setting the max_allowed_packet' variable.; nested exception is java.sql.BatchUpdateException: Packet for query is too large (37183979 > 16777216). You can change this value on the server by setting the max_allowed_packet' variable.`

Where is this 16mb limit set and is it easily changeable? Any drawbacks or possible issues with changing it? Is the global max only applicable to the use of the zip archive tool?

1. 2 Posted by Joel on 09 Jan, 2012 10:25 PM

   

   Hi Travis,

   While the setting within Cascade Server may be 40MB, your MySQL or database settings may be lower. Please take a look at this article for more information and the solution to this issue.

   Thanks!

   Admin Functions

   • Split
   • Remove

2. 3 Posted by Travis F. on 11 Jan, 2012 05:08 PM

   

   That'll do it.

   Thanks.

   Admin Functions

   • Split
   • Remove

3. Travis F. closed this discussion on 11 Jan, 2012 05:08 PM.

Comments are currently closed for this discussion. You can start a new one.