-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
2.2.9
-
None
A very long Message ID seems to be causing error as per example below:
2006-09-29 15:16:08,953 DEBUG [sf.hibernate.type.StringType] nullSafeSet binding '<!~!UENERkVCMDkAAQACALAAAAAAAAAAOKG7EAXlEBqhuwgAKypWwgAAcHN0cHJ4LmRsbAAAAAAAAAAATklUQfm/uAEAqgA32W4AAABDOlxEb2N1bWVudHMgYW5kIFNldHRpbmdzXHNqYWluXExvY2FsIFNldHRpbmdzXEFwcGxpY2F0aW9uIERhdGFcTWljcm9zb2Z0XE91dGxvb2tcT3V0bG9va3JlZC5lZGdpbGl0eS5jb20tMDAwMDAwMDMucHN0ABgAAAAAAAAAGj1XBR9MUk2Ru3uoXrVoKYKAAAAYAAAAAAAAABo9VwUfTFJNkbt7qF61aCkEHiUAAAAAABAAAAAtQYQGo/CpRrKRpF/XUIbmRwAAAFJFOiBDZW50cmFsaXplZCBDb25maWcgbG9nOiAgV2ViIFNlcnZpY2UgdnMuIERhdGFiYXNlIGxvZyAgZGVzdGluYXRpb24A@amberpoint.com>' to parameter: 1
which consequently appears to cause the error below:
2006-09-19 19:00:41,638 ERROR [sf.hibernate.util.JDBCExceptionReporter] logExceptions Data truncation: Data truncated for column 'MESSAGEID' at row 1
After the user located that MESSAGEID in entities.xml file and modified it to a shorter string things seems to be working OK.
He did some further research into the problem and discovered that a "Recall" message submitted by an email sender is the cause of a huge messageId within Confluence. Note that this message also has an attachment named "winmail.dat". I'm not sure if the attachment has anything to do with the naming problem.
In his case, the message was supposed to be recalled from Confluence's email archive.
Can we please look into this matter to confirm that Confluence can handle long message IDs and what are the limits as for the string length?
Thanks,
Ivan
[CONFSERVER-7109] "Recall" message generated by an e-mail client generating extensively long messageId breaking Confluence import
Jim Dibble
added a comment - Note that this error occurred when I was attempting to migrate from one copy of the wiki to another.
The "recall" email message was archived in a Confluence 2.2.2 instance on WindowsXP/Tomcat Standalone/HyperSonic.
I exported from this wiki, and attempted to import into a Confluence 2.2.9 instance on RedHatLinux/Tomcat Standalone/MySQL.
So, the HyperSonic database was clearly able to store the long message ID for the email message, but the MySQL database was not. Or, there was some regression between Confluence 2.2.2 and 2.2.9.
Jim Dibble
added a comment - Note that this error occurred when I was attempting to migrate from one copy of the wiki to another.
The "recall" email message was archived in a Confluence 2.2.2 instance on WindowsXP/Tomcat Standalone/HyperSonic.
I exported from this wiki, and attempted to import into a Confluence 2.2.9 instance on RedHatLinux/Tomcat Standalone/MySQL.
So, the HyperSonic database was clearly able to store the long message ID for the email message, but the MySQL database was not. Or, there was some regression between Confluence 2.2.2 and 2.2.9. 
Fixed.
Very long message ids (longer than 255) are truncated.
Agnes.