cancel
Showing results for 
Search instead for 
Did you mean: 

High Volume Files - Alfresco Issues

ediez
Champ in-the-making
Champ in-the-making
Hi People,

I've been testing the Alfresco repository with high volumes of files/folders. I've been trying to upload 3GB folders and I get a handful of errors from the Application Server Console. I'll list herein some of them:

- org.alfresco.service.cmr.repository.TemplateException: Error during processing of the template 'No nodes selected'. Please contact your system administrator.

- Caused by: freemarker.template.TemplateModelException: No nodes selected

- Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "alf_child_assoc_parent_node_id_key"


(Full stack traces available upon request)

Also, I've found out that a 'big' space cannot be deleted from the web interface, as the http request doesn't go through. It only works if done via an interface such as FTP.

What I'm trying to find out is how Alfresco will behave when big files and folders are uploaded to the repository and I can tell that I'm a little bit concerned because of these findings.

- Alfresco Community 2.1
- PostgreSQL Database
- Tomcat 6.0

If anybody need additional info, please let me know
12 REPLIES 12

steve
Champ in-the-making
Champ in-the-making
Hi,

You can look in our bug tracking system for fixed bugs.
http://issues.alfresco.com

Steve

jzulu2000
Champ in-the-making
Champ in-the-making
I'm having the same problem uploading files using ftp. It happens when loading a big number of files, and alfresco slows down all the following request.
Before the problem occurrs, the avg time creating a document is 120 ms; after the first occurrence of the error the avg increments to 2300 ms.. it's almost 20 times the normal time.

jzulu2000
Champ in-the-making
Champ in-the-making
This problem happened to me when I was trying to save two documents with the same name to alfresco to the same folder at the time, using 2 diferent ftp sessions…
The first ftp session creates the document in memory, but before it persist it, the second session creates it to… then the first session persists it, and after that the second one does it to and the exception is thrown..

the same problem occurrs for example when creating two times the times same folder concurrently.

I think it is because of the hibernate delay to persist the data to the database and make it available to the other sessions.