Issue: Packet for query is too large in Release

Issue

You receive the following error when running a query in Release:

2021-12-30 00:00:25.553 [scheduler-pool-1-thread-96] {} ERROR c.x.x.s.ArchivingScheduleService -
   Could not archive release [Folder3148d35cd8d34f5d9a511f21d2ffd0b0/Releaseffeb9175c3fd45888a0b17a
   30541beff]: PreparedStatementCallback; SQL [UPDATE RELEASES
SET
releaseJson = ?,
activityLogs = ?,
preArchived = ?
WHERE releaseId = ?]; Packet for query is too large (19995804 > 16777216). You can change
   this value on the server by setting the max_allowed_packet' variable.; nested exception is
   com.mysql.jdbc.PacketTooBigException: Packet for query is too large (19995804 > 16777216).
   You can change this value on the server by setting the max_allowed_packet' variable.
org.springframework.dao.TransientDataAccessResourceException: PreparedStatementCallback; SQL [UPDATE
   RELEASES
SET
releaseJson = ?,
activityLogs = ?,
preArchived = ?
WHERE releaseId = ?]; Packet for query is too large (19995804 > 16777216). You can change this value
   on the server by setting the max_allowed_packet' variable.; nested exception is com.mysql.jdbc.
   PacketTooBigException: Packet for query is too large (19995804 > 16777216). You can change this
   value on the server by setting the max_allowed_packet' variable.

Cause

The Issue is related to the MySQL Database where max_allowed_packet is set to a lower value than what the application is trying to pass or fetch.

Workaround/Resolution Action

Increase the max_allowed_packet in the MySQL configuration file(my.ini or my.cnf) by adding the following line under [mysqld] section and then restart the MySQL service.

max_allowed_packet=512M