Details
-
Improvement
-
Resolution: Won't Fix
-
Trivial
-
None
-
None
-
None
-
Magnolia EE 3.5.4, Tomcat 5.5
Description
Magnolia requires a lot of heap (depending on persistence manager and version settings too) and so the "Out Of Memory" error occurs every once and then.
Since magnolia_control.sh by default sets the "CATALINA_OPTS" properties, why not display them on startup of Magnolia?
magnolia_control.sh calls startup.sh which launches catalina.sh.
I suggest that we add the line
echo "Using CATALINA_OPTS: $CATALINA_OPTS"
to the "Execute The Requested Command". The section will look like follows:
- ----- Execute The Requested Command -----------------------------------------
- Bugzilla 37848: only output this if we have a TTY
if [ $have_tty -eq 1 ]; then
echo "Using CATALINA_BASE: $CATALINA_BASE"
echo "Using CATALINA_HOME: $CATALINA_HOME"
echo "Using CATALINA_TMPDIR: $CATALINA_TMPDIR"
if [ "$1" = "debug" -o "$1" = "javac" ] ; then
echo "Using JAVA_HOME: $JAVA_HOME"
else
echo "Using JRE_HOME: $JRE_HOME"
fi
echo "Using CATALINA_OPTS: $CATALINA_OPTS"
fi
This will extend the output to show something like this:
Using CATALINA_BASE: /Applications/Mg354/apache-tomcat-5.5.25
Using CATALINA_HOME: /Applications/Mg354/apache-tomcat-5.5.25
Using CATALINA_TMPDIR: /Applications/Mg354/apache-tomcat-5.5.25/temp
Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Using CATALINA_OPTS: -Xms512M -Xmx1024M -Djava.awt.headless=true
allowing to easily see what additional options, like e.g. Heap, has been set.