Our migration process currently calls the SOAP API-M client. During a
recent migration test, there was a 43MB object being exported. The
first attempts to export it failed with java.lang.OutOfMemory exceptions
during the Base64 decode of the SOAP attachment. After further research,
we found that increasing the max heap size to 1GB allowed the object to
be exported.
That object ended up needing > 500MB of heap to complete the export (as
observed from jvisualvm during the test). As a workaround we moved over
to the REST version of API-M based upon advice from posts to this list
in May of last year. The export now completes and stays below 20MB of
heap space the whole time.
We are running on Fedora 3.2, so I don't know if the same issue is
present in 3.4.1, but I could imagine that others will encounter this
for any operation that uses a SOAP attachment with Axis 1.3. I did find
several other reports describing this problem outside of the Fedora
community from those using Axis 1.3 directly.
Are there any other considerations or alternatives we should explore for
exporting large files?
Regards,
Rob
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
