Hi Hartmut, The explanation of what you see in the log is probably as follows: - OOME during copying the transport file into output stream, meant that the output have been in the very least truncated and most likely the ExchangeException have been throws, but since system ran out of memory it might not have been possible to store the exception in the list or errors and if that list stayed empty system was fooled to thinking there was no execption at all ... whatever happened afterwards the "success" message at the end is bogus.
Sorry if you mentioned that already and I just missed the info, but can you tell me what exact version of Magnolia are you using? Also just out of the interest, what was the size of the video file you tried to activate? Thanks, Jan On Wed, 2009-07-15 at 12:09 +0200, Hartmut Kern (It-Gruppe) wrote: > Hi Grégory, Ruben, > > I changed catalina.sh so it sets the Catalina_Opts and echo what it set: > > /usr/local/magnoliablabla/apache-tomcat-5.5.27/bin/catalina.sh start > Using CATALINA_BASE: /usr/local/magnoliablabla/apache-tomcat-5.5.27 > Using CATALINA_HOME: /usr/local/magnoliablabla/apache-tomcat-5.5.27 > Using CATALINA_TMPDIR: /usr/local/magnoliablabla/apache-tomcat-5.5.27/ > temp > Using CATALINA_OPTS: -XX:MaxPermSize=256M -Xms1024M -Xmx2048M - > Djava.awt.headless=true -d64 > Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/ > Versions/1.5/Home > > Its better in my social enviroment to use Catalina-Opts, because our > Network-People allways click: tomcat. Ok. catalina.sh start. And they > have to do the job to restart all our services, if something fails. > So I have to configure it in a standard way.... > > Any suggestions? > > So, I did a new trial of activation. Here are the statistics. The > result was a little bit confusing, as you can see: > 2009-07-15 11:45:18,932 INFO > info.magnolia.module.ModuleManagerImpl : Starting module > adminInterface > Exception in thread "Thread-73" java.lang.OutOfMemoryError: Java heap > space > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) > at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java: > 61) > at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1026) > at org.apache.commons.io.IOUtils.copy(IOUtils.java:999) > at > info > .magnolia.module.exchangesimple.Transporter.transport(Transporter.java: > 134) > at > info > .magnolia > .module.exchangesimple.SimpleSyndicator.activate(SimpleSyndicator.java: > 162) > at info.magnolia.module.exchangesimple.SimpleSyndicator > $2.run(SimpleSyndicator.java:117) > at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:613) > 2009-07-15 12:03:03,315 > INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: > activation succeeded [/mediathek/video/flash/department1/einstein/ > einstein1000kbps] > > > Stats: > > Begin activation: 11:52 CPU 40% 109 Threads 4GB of 8GB used. > 11:54 CPU 90% 109 Threads > 11:57 CPU 97% 109 Threads 7.96GB of 8GB used. > 12:00 CPU 40% 109 Threads 4GB of 8GB used. > > The process used 540M physical Ram and 5.01 Gb virtuell Ram(?) > > Any suggestions? > > > Hartmut > > > 11:52 > Am 14.07.2009 um 21:00 schrieb Grégory Joseph: > > > > > > > On Jul 14, 2009, at 7:34 PM, Hartmut Kern wrote: > > > >> > >> Hi Grégory, > >> > >> yes, that's obvious. So, the context as I can see it: > >> I used magnolia_control.sh and changed the standard opts into mine. > >> Then I started tomcat with the shell-scriüpt: magnolia_control.sh. > >> (Downloaded and used the normal bundle with tomcat, installed it > >> in /usr/local/...) > > > > Right, that's the information that was missing to make sure we were > > "clean". > > > > On Jul 14, 2009, at 7:51 PM, Ruben Reusser wrote: > >> On another note: > >> > >> tomcat suggests to create a setenv.bat or setenv.sh file in the > >> tomcat/bin folder and set your custom parameters there instead of > >> the magnolia_control.sh file (the setenv is recommended to handle > >> setting parameters in order to better run multiple instances of > >> tomcat on one server) > > > > > > Tomcat doesn't know about magnolia_control.sh ;) It's just a handy > > wrapper around the default tomcat scripts; setenv is indeed a good > > option for someone who's used to Tomcat, but it won't change > > Hartmut's problem. Unless something in his environment sets > > CATALINA_OPTS before running magnolia_control.sh, it'll come down to > > the same thing... unless: > > > > Hartmut: Again, just to make sure your parameters are correctly > > taken into account: > > * could check if you have a setenv(.sh) ? As Ruben suggests, it's > > another approach to set the environment for Tomcat.. if you had such > > a file, it could be interfering with the settings you made in > > magnolia_control.sh > > > > * what do you get if you do > > echo $JAVA_OPTS > > echo $CATALINA_OPTS > > in your shell, *before* starting Magnolia ? > > > > Cheers, > > > > -g > > > > > > ---------------------------------------------------------------- > > 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]> ----------------------------------------------------------------
