as a general precaution, I always end up serving larger files from
outside magnolia (direct serving from apache) but keep the uploading of
the file and a file reference in magnolia.
activation and export create XMLs, the XMLs and depending on how they
are created (string buffer or directly to file) you always run into a
risk of running out of memory.
But that's just me. Others may have a vastly different opinion on this
subject.
Ruben
Hartmut Kern wrote:
Hi Grégory, Ruben,
I changed catalina.sh so it sets the Catalina_Opts and echo what it set:
Which is exactly what you shouldn't do. Use setenv, it's the
standard/preferred of doing these things, OR use magnolia_control.sh,
which I personally favor, amongst other things because it does *not*
set does settings when you shut tomcat down, for instance. (which is
helpful if you have jmx or debug settings for instance)
Thank you for this. So I will return to magnolia_control.sh or setenv.
By the way: Problem didn't changed. It is still there.
As a summary, do you or others think, that there is limitation of
serving file over Jackrabbit / Magnolia, where I have to say: Ok:
Files with a max. of 450 MB are ok.
All other (>450MB) have to be served over Apache and linked in
Magnolia over URL.
?????
Hartmut
-g
----------------------------------------------------------------
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]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
