DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38353>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38353

           Summary: Unable to post large(>2GB) files using Slide API
           Product: Slide
           Version: 2.0
          Platform: All
        OS/Version: Windows 2000
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Stores
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


We are not able to store large files > 2GB when we use File Content Storage
(TxFileContentStore Storage).
Any file less then 2GB we are able to store into file system successfully.

When storing >2GB, we encounter the below pasted exception:

org.apache.slide.common.ServiceAccessException: Service TxFileStore at E:/Textup
loadtest/slide/store/content  working on E:/Textuploadtest/slide/work/content ac
cess error : Thread-19-1137482059804-60: Failed to undo change / create of '/113
7481500664.54_1.0' (ERR_SYSTEM)org.apache.slide.common.ServiceAccessException: S
ervice TxFileStore at E:/Textuploadtest/slide/store/content  working on E:/Textu
ploadtest/slide/work/content access error : Thread-19-1137482059804-60: Failed t
o undo change / create of '/1137481500664.54_1.0' (ERR_SYSTEM)
        at org.apache.slide.store.txfile.AbstractTxFileStoreService.throwInterna
lError(AbstractTxFileStoreService.java:433)
        at org.apache.slide.store.txfile.TxFileContentStore.storeRevisionContent
(TxFileContentStore.java:127)
        at org.apache.slide.store.txfile.TxFileContentStore.createRevisionConten
t(TxFileContentStore.java:85)
        at org.apache.slide.store.AbstractStore.createRevisionContent(Unknown So
urce)
        at org.apache.slide.store.ExtendedStore.createRevisionContent(Unknown So
urce)
        at org.apache.slide.store.BindingStore.createRevisionContent(BindingStor
e.java:556)
        at org.apache.slide.store.BindingStore.createRevisionContent(BindingStor
e.java:561)
        at org.apache.slide.content.ContentImpl.create(ContentImpl.java:538)
        at com.hyperion.eie.common.cms.WebdavPutMethod.putNewResource(Unknown So
urce)
        at com.hyperion.eie.common.cms.WebdavPutMethod.run(Unknown Source)
        at com.hyperion.eie.common.cms.WebdavPutMethod.executeMethod(Unknown Sou
rce)
        at com.sample.fileContent.Repository.uploadFile(Repository.java)

When debugging the slide code for the same we came to know the exception are 
thrown in the below code for the condition (if (contentLength != -1 && 
contentBytes != contentLength)), basically the contentLenght & contentBytes are 
not matching which should be same to store the file.

/*
In TxFileContentStore.java there are two parameters:
long contentBytes = FileHelper.copy(is, os);
long contentLength = revisionDescriptor.getContentLength();
And a condition:
if (contentLength != -1 && contentBytes != contentLength) 
{
   rm.deleteResource(getActiveTxId(), revisionUri);
   throwInternalError("Content length does not match expected");
}    
*/

When the above condition(contentLength and contentBytes) fails, the flow will 
go to delete the resource(rm.deleteResource) which is not yet stored in 
repository and the exception what we pasted above is thrown from 
rm.deleteResource() which is not actually the real cause to store large files. 
So the actuall cause what we found is value of the contentLength and 
contentBytes are not matching.

Please let us know if any one has already faced/fixed this issue in Slide2.0.
We are also trying to fix this, but it would help us if any one has already 
solution for this.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to