LiveCycle and MySQL - max_allowed_packet problem

| No Comments

While deploying LiveCycle and initializing its tables against the MySQL database, you might run into the following error during the deployment of the Document Service Components (DSCs):
com.mysql.jdbc.PacketTooBigException: Packet for query is too large (1499558 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.

Please see here for a discussion about this at the MySQL website. According to MySQL, 'max_allowed_packet' controls the "largest possible packet that can be transmitted to or from a MySQL 5.0 server or client". The default value is 1M (1 MB). LiveCycle DSC deployment requires this to be at least 50M (50 MB).

This can be set in the my.ini configuration file for MySQL as follows:
max_allowed_packet=50M

It can also be configured using MySQL Administrator, the GUI Admin Tool for MySQL.

Leave a comment

About this Entry

This page contains a single entry by Jayan Kandathil published on November 25, 2008 12:35 PM.

Running LiveCycle as a Non-root User on AIX, Solaris and Linux was the previous entry in this blog.

Red Hat Enterprise Linux Packages Required by LiveCycle is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.