Some files are not loaded to Alfresco in initial import, but are successfully imported on a second import

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run a bulk filesystem import with @ 27,000 images
2. run a CMIS query to find the node reference for each imported image
3. notice that this query fails to find a node reference for some images
4. log into Alfresco, go to the expected path (based on the file system path)
5. the image is not in Alfresco at this path
6. run a second filesystem import with only the few images that were not loaded 
by the first import
7. now the images are loaded successfully

What is the expected output? What do you see instead?
Expected: all images loaded successfully during first import
Actual: most images are loaded, however some were not loaded (but were imported 
successfully after another import)

What version of the product are you using? On what operating system?
The version provided with Alfresco 4.0.2.  OS: Red Hat Enterprise Linux

Please provide any additional information below.
I noticed an earlier issue regarding symbolic links on Linux.  I don't believe 
my customer has symbolic links in the path, but I am finding out.

Original issue reported on code.google.com by david.oc...@gmail.com on 3 Jan 2013 at 2:42

[GoogleCodeExporter]

David, are you using the version of the tool available here on this site, or 
the version bundled in Alfresco v4?

Original comment by pmo...@gmail.com on 3 Jan 2013 at 3:27

• Changed state: NeedMoreInfo

[GoogleCodeExporter]

Peter,

It is the version bundled in Alfresco v4.  Shall we try the version from this 
site?  Is it as easy as applying the new amp to the Alfresco war, or is there 
more steps to replace the bundled version with the site version?

Original comment by david.oc...@gmail.com on 3 Jan 2013 at 3:30

[GoogleCodeExporter]

If you're an Alfresco Enterprise subscriber, you can obtain support for the 
bundled version at http://support.alfresco.com/.

Alternatively, you could install the version available here and if you run into 
issues use the mailing list [1] and/or issue tracker [2] to get assistance.

[1] http://groups.google.com/group/alfresco-bulk-filesystem-import
[2] http://code.google.com/p/alfresco-bulk-filesystem-import/issues/list

Original comment by pmo...@gmail.com on 3 Jan 2013 at 4:12

[GoogleCodeExporter]

And yes, installing the version available here is involves deploying the new 
AMP - more detailed instructions are at [1].  The version available here will 
coexist with the bundled version - it uses different URLs and classnames etc. 
so both versions can comfortably reside side-by-side - you could even use both, 
although that probably isn't very useful.

[1] http://code.google.com/p/alfresco-bulk-filesystem-import/wiki/Install

Original comment by pmo...@gmail.com on 3 Jan 2013 at 4:15

[GoogleCodeExporter]

I suppose installing the version available here and letting you know of any 
available issues will be faster than getting adequate support from corporate 
Alfresco!  I will try both using this version and trying to dig decent support 
from support.alfresco.com.

Thanks,
Dave

Original comment by david.oc...@gmail.com on 3 Jan 2013 at 4:57

[GoogleCodeExporter]

Yeah definitely get back in touch if you see the same thing with the Google 
Code version of the tool.  If you can reproduce it at will, it'd be worth 
turning on debug logging for the tool to see if that shines any extra light on 
the problem.  That's described here: 
http://code.google.com/p/alfresco-bulk-filesystem-import/wiki/Troubleshooting

Also, have you run the Environment Validation Tool [1]?  It's possible (though 
unlikely, I think) that this is something environmental, and the EVT is a quick 
& easy way to eliminate some of those possibilities.

[1] http://code.google.com/p/alfresco-environment-validation/

Original comment by pmo...@gmail.com on 3 Jan 2013 at 5:46

[GoogleCodeExporter]

David, did you have better success with the Google Code version of the tool?

I intend to mark this issue resolved if I don't hear back in the next couple of 
weeks.

Original comment by pmo...@gmail.com on 14 Sep 2013 at 10:41

[GoogleCodeExporter]

The Google Code version worked very well.  Also, according to the ticket 
I opened with Alfresco, they have identified and fixed the issue with 
the version bundled with Alfresco 4.

Original comment by david.oc...@gmail.com on 22 Sep 2013 at 9:53

[GoogleCodeExporter]

Great - thanks for the update David.

Original comment by pmo...@gmail.com on 23 Sep 2013 at 1:13

• Changed state: Invalid