In the query database operation, reported the above error, as well as out of Memery heap HACP, because the MySQL max_allowed_packet settings too small caused by, I started to set the 1M, then changed to 20M
MySQL restricts the size of packets accepted by the server according to the configuration file.
Sometimes large inserts and updates are limited by the Max_allowed_packet parameter, resulting in failure.
View current configuration
' %max_allowed_packet% ';
The results shown are:
+--------------------+---------+ | variable_name | Value | +--------------------+---------+ | Max_allowed_packet | 1048576 | +--------------------+---------+
The above description is currently configured to: 1M
Modify method
1. Method 1
You can edit the my.cnf to modify (under Windows My.ini) and modify it in the [Mysqld] section or in the MySQL server configuration section.
Max_allowed_packet = 20M
If you can't find the MY.CNF, you can pass
MySQL--help | grep my.cnf
To find the my.cnf file.
Pro-Test: Modify the/etc/my.cnf file, add configuration, and then restart the MySQL service
2. Method Two
Go to MySQL server
Run in the MySQL command line
Set Global Max_allowed_packet = 2*1024*1024*10
Then shut down this MySQL server link and then enter.
Show VARIABLES like '%max_allowed_packet% ';
See if the next Max_allowed_packet is edited successfully
Experience Summary:
There are no problems with using methods on many machines, but it is not successful to meet a machine.
Using the command line: Set global max_allowed_packet = 16M;
No, but using set global max_allowed_packet = 2*1024*1024*10;
Success, it's depressing.
The problem is finally found, not the problem of the method, is the setup after the command line to exit the login to view, it appears that the value of the system variable is cached after login. However, the configuration INI file is used on this machine.
The
MySQL operational capacity limit issue Error updating database. Cause:com.mysql.jdbc.PacketTooBigException:Packet for query is too large (1082 > 1024x768)