Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Mon, 11 Jun 2012 11:59:44 +0000 (UTC)
From: "Sascha Theves (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <1741487388.2593.1339415985000.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1097001327.7270.1337679281034.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (JCR-3318) BLOB not stored and no exception
 thrown
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sascha Theves commented on JCR-3318:
------------------------------------

@Claus: Thanks for the patch but it seems to be invalid or at least I cannot use it because it is not a valid SVN patch file. Could you provide a valid patch?
                
> 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
>         Attachments: JCR-3318.patch
>
>
> 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