attached an updated (by me) copy of tomcat4, however, memory is not
consumed if OM started after a reboot (2G max for 3 classes, 5 students
each, audio only), but if multiple stop and start is done, all memory is
consumed.
On 10/5/20 3:27 AM, Maxim Solodovnik wrote:
98% of RAM might be an issue
was the memory consumed by java process?
What are the `-Xmx` and `-Xms` parameters for OM?
On Mon, 5 Oct 2020 at 01:29, Denis Noctor <denisnoc...@gmail.com
<mailto:denisnoc...@gmail.com>> wrote:
I experienced this after upgrading to a 5.0.1 snapshot and was
about to follow up a response to Maxim. Not at a computer at the
moment but I experienced exactly the same. I am using Ubuntu
18.04 on AWS with 8 gigs ram. When SSH’ing to my server (with only
one user logged in (me) I noticed RAM usage was 98%...
I downgraded to OM 5 M4 and everything is fine again (but lack the
advantages of the snapshot upgrade)... RAM usage dropped a lot
also... a lot!
Will take some time to compare tomcat3 and tomcat4 on startup,
folder permissions and differences between OM 5 M4 and recent
snapshot.
All the best,
Denis.
Sent from my iPhone
> On Oct 4, 2020, at 9:18 AM, Ali Alhaidary
<ali.alhaid...@the5stars.org <mailto:ali.alhaid...@the5stars.org>>
wrote:
>
> the following scenario is almost always happening:
>
> 1. the user enters the room
>
> 2. connection is not established (fails).
>
> 3. the user turns his mic off.
>
> 4. wait for few seconds.
>
> 5 the user turns his mic on.
>
> 6. connection to media server is established and keeps on even
if the session went for hours.
>
> Looking at log files, I could not locate any ERROR or java
exception or WAR that I assume is related to this case.
>
> Any idea of what is happening?
>
--
Best regards,
Maxim
#!/bin/sh
# set the environment
# JAVA_OPTS="-Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom"
# CATALINA_OPTS=""
# chown -R nobody:nogroup /opt/rooms
export JAVA_OPTS="-Djava.awt.headless=true -DDATA_DIR=/opt/rooms.data
-Djava.security.egd=file:/dev/./urandom"
export JDK_JAVA_OPTIONS="--add-modules java.se --add-exports
java.base/jdk.internal.ref=ALL-UNNAMED --add-opens
java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED
--add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens
java.management/sun.management=ALL-UNNAMED --add-opens
jdk.management/com.sun.management.internal=ALL-UNNAMED"
CATALINA_HOME=/opt/rooms
# set TIME OUT values
# TIMELIMIT=10
# SLEEPTIME=40
# Function to wait until all Tomcat processes are killed
waitForTomcatToDie()
{
PROCESSES=`ps auxwww | grep $HOME | grep 'java' | grep 'tomcat' | grep -v
'grep'`
while [ ! -z "$PROCESSES" ] && [ $SECONDS -lt $TIMELIMIT ] && [ $TIMELIMIT -ne
0 ]; do
echo -n "."
sleep $SLEEPTIME
PROCESSES=`ps auxwww | grep $USER | grep 'java' | grep 'tomcat' | grep -v
'grep'`
done
echo ""
if [ ! -z "$PROCESSES" ]; then
PROCESS_ID=`echo $PROCESSES | awk '{ print $2 }'`
echo "Killing process: $PROCESS_ID"
kill -9 $PROCESS_ID
fi
}
# See how we were called.
case "$1" in
start)
#$CATALINA_HOME/bin/startup.sh
cd ${CATALINA_HOME}
sudo --preserve-env=CATALINA_BASE --preserve-env=JAVA_OPTS -u nobody
${CATALINA_HOME}/bin/startup.sh
;;
# debug)
# DEBUG_PORT=10001
# ;;
stop)
# $CATALINA_HOME/bin/shutdown.sh
$CATALINA_HOME/bin/shutdown.sh
waitForTomcatToDie
echo "...Tomcat stopped."
;;
restart)
$0 stop
echo "...Restarting..."
sleep 8
$0 start
;;
status)
status $PROG -p $PIDFILE
RETVAL=$?
;;
*)
echo $"Usage: $0 {start|stop|restart|status}"
RETVAL=1
esac
exit $RETVAL