Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 22 May 2012 12:47:41 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <570900448.7639.1337690861363.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: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3318?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D132809=
14#comment-13280914 ]=20

Claus K=C3=B6ll commented on JCR-3318:
---------------------------------

Hi. I had the same problem time ago and made only a fast fix for it and for=
got 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 l=
ook at it soon.
               =20
> 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 t=
he content. Now, if do not configure the max_packet_size in MySQL you can o=
nly 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 tha=
n 1MB. Jackrabbit gets now a SQLException for the first time it tries to st=
ore 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 wor=
ks because the InputStream has hit its end and there are no bytes left. Tha=
t 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 datab=
ase.

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