On Thu, 2009-07-16 at 06:25 -0700, Ruben Reusser wrote: > 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.
The export goes into the file and then is streamed from the file directly into the OutputStream of the response. You can check Transporter class to see the details. What puzzles me in the stacktrace from the original issue is that in this case the implementation of java.net.Connection was using ByteArrayOutputStream as the output stream for the request ... probably to gauge the total size of the content being sent over so it could communicate the total length for the receiver. That means that the "chunked" transfer encoding was not used ... if you manage to change that in the configuration the issue might go away. This kind of info is usually negotiated between sender and receiver (in this case the app server on which author instance is running and app server on which public instance is running). HTH, Jan > > 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]> > ---------------------------------------------------------------- -- Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
