Bug #29063 mgmapi: connect timeout set incorrectly

Submitted: 13 Jun 2007 2:59 Modified: 19 Jun 2007 12:08
Reporter: Stewart Smith Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.4-a_drop6p8, 5.1.19 OS:Any
Assigned to: Stewart Smith CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

  • On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
  • On windows use WinZip or a similar utility to split the large file
[13 Jun 2007 5:57] Stewart Smith
Test case

Attachment: bug29063_mgmapi_connect_test.patch (text/x-patch), 2.78 KiB.

[13 Jun 2007 5:57] Stewart Smith
patch

Attachment: bug29063_connect_timeout.patch (text/x-patch), 706 bytes.

[13 Jun 2007 6:04] Stewart Smith
patch v2 - round up

Attachment: bug29063_connect_timeout.patch (text/x-patch), 712 bytes.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.