[
https://issues.apache.org/jira/browse/OPENMEETINGS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781292#comment-13781292
]
SebastianWagner commented on OPENMEETINGS-808:
----------------------------------------------
At the moment our default instructions say to run the red5.sh. And I think its
a good thing to supply a script that really sets the required defaults for the
user, instead of needing them to change something. That just leads to a lot of
emails to the mailing list or frustration.
I think our default options should be *ready-to-run* and not something where
you immediately need to read the docs because the application hangs.
So maybe we can patch the red5.sh to make those options available by default.
Or we supply our own custom shell .sh and .bat to start red5.
At the moment the ant task that starts red5 for selenium is already using the
red5-highperf.sh.
> 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)
