[
https://issues.apache.org/jira/browse/OPENMEETINGS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781263#comment-13781263
]
Maxim Solodovnik commented on OPENMEETINGS-808:
-----------------------------------------------
exec for selenium can be updated as follows:
<exec dir="${dist.dir}/testred5" executable="/bin/bash"
osfamily="unix" output="${dist.dir}/testred5/red5_system.log">
<env key="JVM_OPTS"
value="-XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled
-XX:MaxPermSize=512M -Xmx1024m -Xms512m -Xss256k -XX:+AggressiveOpts
-XX:+DisableExplicitGC -XX:ParallelGCThreads=4 -XX:+UseConcMarkSweepGC
-Xverify:none -XX:+TieredCompilation -XX:+UseBiasedLocking -XX:+UseStringCache
-XX:+UseParNewGC -XX:SurvivorRatio=16 -XX:TargetSurvivorRatio=90
-XX:MaxTenuringThreshold=31 -Djava.net.preferIPv4Stack=true
-XX:InitialCodeCacheSize=8m -XX:ReservedCodeCacheSize=32m
-Dorg.terracotta.quartz.skipUpdateCheck=true"/>
<arg value="red5.sh"/>
</exec>
> Installation using Derby default database configuration seems to have
> performance issues
> ----------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-808
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-808
> Project: Openmeetings
> Issue Type: Bug
> Reporter: SebastianWagner
> Attachments: DerbyHangsAfterInstallationInLogin.png
>
>
> When doing the default installation option using derby it seems the
> application hangs
> Also if you use then commands like red5-highperf.sh the memory settings don't
> fix the issues.
> And red5-shutdown.sh throws an error that it cannot shut down the server.
> We should either fix that or get rid of Derby. Its a quite user experience to
> have the very first thing in the installation to see failing.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
