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:27:02 UTC
[jira] [Commented] (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=13780703#comment-13780703 ]
SebastianWagner commented on OPENMEETINGS-808:
----------------------------------------------
My behaviour is the following:
Running with red5.sh
I can navigate to the WebInstaller, go through all points, and it completes.
But when you then click on the link to navigate to the application after installer was successful,
there is a Perm Gem Space - Out of memory error in the java log and the application will redirect to a page with "Internal Server Error"
Running with red5-highperf.sh
Same as red5.sh but the Perm Gem Space - Out of memory error, but instead you just get a partially loaded page.
I never succeeded to run the installer and login using Apache Derby with the current revision.
> 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
>
> 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