You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Claus Köll (JIRA)" <ji...@apache.org> on 2012/05/22 14:49:41 UTC

[jira] [Comment Edited] (JCR-3318) BLOB not stored and no exception thrown

    [ https://issues.apache.org/jira/browse/JCR-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280914#comment-13280914 ] 

Claus Köll edited comment on JCR-3318 at 5/22/12 12:49 PM:
-----------------------------------------------------------

Hi. I had the same problem time ago and made only a fast fix for it and forgot to create a jira issue. Thank you to bring them up now.
If you have already a patch feel free to attach it otherwise i will have a look at it soon.
                
      was (Author: c_koell):
    Hi. I had the same problem time ago and made only a fast fix for it and forgot to create a jira issue. Thank you to bring them up now.
If you have already a path feel free to attach it otherwise i will have a look at it soon.
                  
> BLOB not stored and no exception thrown
> ---------------------------------------
>
>                 Key: JCR-3318
>                 URL: https://issues.apache.org/jira/browse/JCR-3318
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.2.10
>            Reporter: Sascha Theves
>
> Configure Jackrabbit to use a DbDatastore and a MySQL database to store the content. Now, if do not configure the max_packet_size in MySQL you can only store Blobs that are smaller than 1MB (default). If you now add a Node in Jackrabbit that has a binary property and try to store a Blob larger than 1MB. Jackrabbit gets now a SQLException for the first time it tries to store the binary value. But there is failover mechanism implemented that now tries to persist the bin value for a second time. Now storing the value works because the InputStream has hit its end and there are no bytes left. That results now in an empty binary value that is stored and the client doesn`t get informed about that.
> Same problem occurs if you hit the table space limit with an oracle database.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira