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]>
----------------------------------------------------------------
