Bug #1640 can't insert big blob

• Submitted: 23 Oct 2003 12:45
• Modified: 24 Nov 2003 14:42
• Reporter: Harald
• Status: No Feedback
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 4.0.16
• OS: Windows (win2k)
• CPU Architecture: Any

[23 Oct 2003 12:45] Harald

Description:
I can't insert pictures into my database which are somewhat bigger than 400 kb. 

The problem exist with mysqlcc 0.9.3 (and also with a Java client connected with the J/Connector 3.0.7 up to 3.0.9). 

The server cancel the connection during storing the data and the client gives the message: ERROR 2006: MySQL server has gone away. 

The error doesent depends on the table type if have tested myIsam and InnoDD.

BTW. The max_allowed_packet is set to 128M on the client and the server.

How to repeat:
Try to store a jpg > 400 kb in a mediumblob or longblob with the mysqlcc image viewer.

[24 Oct 2003 12:09] Indrek Siitan

Has server acknowledged the max_allowed_packet setting? What does
the following command output:

  show variables like 'max_allowed_packet';

[24 Oct 2003 14:42] Harald

Hi Indrik!

show variables like 'max_allowed_packet';

+--------------------+-----------+
| Variable_name      | Value     |
+--------------------+-----------+
| max_allowed_packet | 134216704 |
+--------------------+-----------+

but, I found that the variable net_buffer_length 

+-------------------+---------+
| Variable_name     | Value   |
+-------------------+---------+
| net_buffer_length | 1048576 |
+-------------------+---------+

but in my.ini

[mysqld]
set-variable=max_allowed_packet=128M
set-variable=net_buffer_length=16M

However, the problem exist even with smaller files than << 1M.

Thanks Harald

[14 Feb 2005 22:54] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".