incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLEREZZA-190) Clerezza + Apchae Felix 2.0.4 very slow & out of memory
Date Wed, 14 Apr 2010 08:28:54 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856799#action_12856799
] 

Karl Pauls commented on CLEREZZA-190:
-------------------------------------

The tricky thing with all the stacktraces we have as of now is that they don't seem to be
the cause of the issue. Something is eating all the memory and as a consequence stuff starts
to go wrong in arbitrary places. We need to find whatever is eating the memory in the first
place. It might be very well be releated to the security provider. Can you try to run a memory
profiler and see whether you can spot what is holding all the memory?

> Clerezza + Apchae Felix 2.0.4  very slow & out of memory
> --------------------------------------------------------
>
>                 Key: CLEREZZA-190
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-190
>             Project: Clerezza
>          Issue Type: Bug
>         Environment: Windows XP 2.6 GHz 3,25 GB RAM
>            Reporter: Oliver Strässer
>            Priority: Blocker
>
> I start the apache clerezza with tho following command
> java -Xmx1000m  -jar "O:\trialox-launcher\org.apache.clerezza.platform.launcher.sesame-0.5-incubating-SNAPSHOT.jar"
-L DEBUG -P 8080
> the startup needs over 4 minutes and the compiling of scala server pages needs very long
too. 
> since startup, where the apache clerezza system needs 150 MB RAM the System / Felix -
whoever - needs 1,2 GB RAM and becomes very very slow. 
> Developing is so not so cool (for example developing ssp's).
> After a while (in my case 1 hour ), i got the following exception.
> The same code works (without a little thing in sparql - wich is the reason why  I need
the newest launcher) in an old version (org.apache.clerezza.platform.launcher.sesame-0.5-incubating-20100407.180339-33.jar)
perfectly.
>  [33234784@qtp-161080-18 - /system/console/res/lib/jquery-1.3.2.js] WARN org.mortbay.jetty
- Error for /system/console/res/lib/jquery-1.3.2.js
> java.lang.OutOfMemoryError: Java heap space
>         at java.util.zip.InflaterInputStream.<init>(Unknown Source)
>         at java.util.zip.ZipFile$1.<init>(Unknown Source)
>         at java.util.zip.ZipFile.getInputStream(Unknown Source)
>         at java.util.zip.ZipFile.getInputStream(Unknown Source)
>         at java.util.jar.JarFile.getInputStream(Unknown Source)
>         at org.apache.felix.framework.cache.JarContent.getEntryAsStream(JarContent.java:179)
>         at org.apache.felix.framework.ModuleImpl.getInputStream(ModuleImpl.java:1127)
>         at org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:124)
>         at org.apache.felix.framework.URLHandlersBundleURLConnection.getContentType(URLHandlersBundleURLConnection.java:178)
>         at org.ops4j.pax.web.service.jetty.internal.ResourceServlet.doGet(ResourceServlet.java:94)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
>         at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
>         at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:64)
>         at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>         at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
>         at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.handle(HttpServiceContext.java:111)
>         at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:64)
>         at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>         at org.mortbay.jetty.Server.handle(Server.java:322)
>         at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
>         at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
>         at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
>         at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>         at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>         at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>         at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
> [24089652@qtp-161080-15 - /system/console/res/lib/reset-min.css] WARN org.mortbay.jetty
- /system/console/res/lib/reset-min.css
> java.lang.NullPointerException
>         at java.util.zip.Inflater.ensureOpen(Unknown Source)
>         at java.util.zip.Inflater.getBytesWritten(Unknown Source)
>         at java.util.zip.ZipFile$1.available(Unknown Source)
>         at org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:125)
>         at org.apache.felix.framework.URLHandlersBundleURLConnection.getContentType(URLHandlersBundleURLConnection.java:178)
>         at org.ops4j.pax.web.service.jetty.internal.ResourceServlet.doGet(ResourceServlet.java:94)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
>         at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
>         at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:64)
>         at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>         at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
>         at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.handle(HttpServiceContext.java:111)
>         at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:64)
>         at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>         at org.mortbay.jetty.Server.handle(Server.java:322)
>         at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
>         at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
>         at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
>         at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>         at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>         at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>         at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message