You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/02/05 05:44:57 UTC

[jira] [Closed] (OPENMEETINGS-808) Installation using Derby default database configuration seems to have performance issues

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik closed OPENMEETINGS-808.
-----------------------------------------


Closing resolved issues related to 3.0.0 release

> 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
>            Assignee: Maxim Solodovnik
>             Fix For: 3.0.0 Apache Release
>
>         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.5#6160)