[
https://issues.apache.org/jira/browse/OPENMEETINGS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780712#comment-13780712
]
SebastianWagner commented on OPENMEETINGS-808:
----------------------------------------------
I have attached a screenshot (
DerbyHangsAfterInstallationInLogin.png), that is how it looks like when I run
red5-highperf.sh and try to login after the installation.
And in the log you find:
SEVERE:Memory usage is low, parachute is non existent, your system may start
failing.
java.lang.OutOfMemoryError: PermGen space
Exception in thread "http-nio-0.0.0.0-5080-Acceptor-0"
java.lang.OutOfMemoryError: PermGen space
at java.lang.Throwable.getStackTraceElement(Native Method)
at java.lang.Throwable.getOurStackTrace(Throwable.java:591)
at java.lang.Throwable.printStackTrace(Throwable.java:462)
at java.lang.Throwable.printStackTrace(Throwable.java:451)
at
org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:831)
at java.lang.Thread.run(Thread.java:680)
DEBUG 09-28 17:49:36.925 PageAccessSynchronizer.java 156398 211
org.apache.wicket.page.PageAccessSynchronizer [http-nio-0.0.0.0-5080-exec-6] -
'http-nio-0.0.0.0-5080-exec-6' released lock to page with id '9'
DEBUG 09-28 17:49:38.106 PageAccessSynchronizer.java 157579 219
org.apache.wicket.page.PageAccessSynchronizer [http-nio-0.0.0.0-5080-exec-6] -
'http-nio-0.0.0.0-5080-exec-6' notifying blocked threads
Sep 28, 2013 5:49:38 PM org.apache.tomcat.util.net.NioEndpoint$SocketProcessor
run
SEVERE:
java.lang.OutOfMemoryError: PermGen space
> 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
