You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (JIRA)" <ji...@apache.org> on 2013/09/28 07:57:07 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=13780715#comment-13780715 ] 

SebastianWagner edited comment on OPENMEETINGS-808 at 9/28/13 5:56 AM:
-----------------------------------------------------------------------

After a restart of the openmeetings application you can login and use the app fine.

It really seems like we have a memory leak in the installation process, maybe something is loaded in the memory but never free'ed.
                
      was (Author: swagner):
    After a restart the application is then fine.

It really seems like we have a memory leak in the installation process, maybe something is loaded in the memory but never free'ed.
                  
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira