Affects Version/s: 7.0.0pre0, 7.0.0pre1, 7.0.0pre2, 7.0.0pre3, 7.0.0pre4, 7.0.0.pre5, 7.0.0.RC4, 7.0.0.RC5, 7.0.0.RC6, 7.0.0, 7.0.1
Fix Version/s: 7.0.2
Environment:Centos 5.4 32/64bit, Jetty 7.0.0.RC5, MySQL 5.1/MySQL Cluster 7.0.9
Number of attachments :
MySQL has limits on the size of data you can store in blobs of various types and although using blob works it fails when the session data exceeds 64kb. To be sane suggest longblob to agree with postgres 4Gb limit.
blob => 65535 bytes (Approx 64kb)
mediumblob =>16777215 bytes (Approx 16Mb)
longblob => 4294967295 bytes (Approx 4Gb)
126 public String getBlobType ()
Temporary work around either pre-create the JettySessions table or run following on database :
alter table JettySessions modify column map longblob;
Using a longblob appears to work fine up to around 32-36Mb in session data but not sure what the issue is when the session data gets this large. May just be a server config issue rather than a real issue.
Note in my.conf on MySQL you will need to increase the default max_allowed_packet size from 1M to test the limits.
- The maximum size of a query packet the server can handle as well as
- maximum query size server can process (Important when working with
- large BLOBs). enlarged dynamically, for each connection.
max_allowed_packet = 1G