We are using JackRabbit 1.6.2 (Magnolia 4.4.2).  You can see the full stack 
trace at http://sptci.com/uploads/magnolia/sha.txt

Should I post this to the jR mailing list as well?  It looks like this is a 
pure JR issue and not related to Magnolia directly.  I am not sure how well 
supported 1.6.2 is, JR current version is 2.2.5

Rakesh

From: Jan Haderka 
<[email protected]<mailto:[email protected]>>
Reply-To: Magnolia User-List 
<[email protected]<mailto:[email protected]>>
Date: Mon, 14 Mar 2011 03:33:41 -0500
To: Magnolia User-List 
<[email protected]<mailto:[email protected]>>
Subject: Re: [magnolia-user] Error while uploading image to dms

That seems to me like a JackRabbit DataStore problem. Probably there is file in 
the data store with the same signature, but with the permissions that do not 
allow access.
Check the data store. If there is a full stacktrace to that error, please 
provide it together with the exact version number of JackRabbit that you use.

HTH,
Jan

On Mar 11, 2011, at 10:59 PM, Rakesh Vidyadharan wrote:

We ran into a weird issue while trying to update an existing image in the DMS 
(standard workflow is to remove the file attachment and re-upload a new file).  
We are able to add/upload other images, but one image file continually fails 
with the following error:

2011-03-11 15:54:05,501 ERROR 
nfo.magnolia.module.admininterface.SaveHandlerImpl: Could not add record: SHA-1 
collision: 
/data/cms/magnolia/prod/webapps/magnoliaAuthor/repositories/magnolia/repository/datastore/07/e1/f4/07e1f4d5cff4387934f6ecf66ae03b2d239d8469
org.apache.jackrabbit.core.data.DataStoreException: Could not add record: SHA-1 
collision: 
/data/cms/magnolia/prod/webapps/magnoliaAuthor/repositories/magnolia/repository/datastore/07/e1/f4/07e1f4d5cff4387934f6ecf66ae03b2d239d8469:
 SHA-1 collision: 
/data/cms/magnolia/prod/webapps/magnoliaAuthor/repositories/magnolia/repository/datastore/07/e1/f4/07e1f4d5cff4387934f6ecf66ae03b2d239d8469


Does that indicate that the checksum for the image being uploaded is through 
coincidence the same as an existing image?  Is there any way to get around 
this?  Funnily enough, we are able to upload the image in question to the 
public instances, but not on the admin instance (I am not sure if there are 
unactivated images on the author instance).

Thanks in advance for all help in resolving this issue.

Rakesh


________________________________
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 
<[email protected]<mailto:[email protected]>>
----------------------------------------------------------------




________________________________
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 
<[email protected]<mailto:[email protected]>>
----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to