karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-2343) Installing Cellar 2.3.0 cellar-event crashes Karaf 2.3.1 after a few seconds...
Date Sun, 16 Jun 2013 06:54:20 GMT

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

Jean-Baptiste Onofré updated KARAF-2343:
----------------------------------------

    Fix Version/s: cellar-2.3.1
                   cellar-3.0.0
    
> Installing Cellar 2.3.0 cellar-event crashes Karaf 2.3.1 after a few seconds...
> -------------------------------------------------------------------------------
>
>                 Key: KARAF-2343
>                 URL: https://issues.apache.org/jira/browse/KARAF-2343
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-features
>    Affects Versions: cellar-2.3.0
>         Environment: Windows 7, Karaf 2.3.1, Cellar 2.3.0
>            Reporter: Ryan Moquin
>            Assignee: Jean-Baptiste Onofré
>            Priority: Blocker
>             Fix For: cellar-3.0.0, cellar-2.3.1
>
>         Attachments: karaf-2.3.1_cellar-2.3.0-memory_problem.JPG
>
>
> After I installed cellar-event (it seems like it should be installed), my cpu usage went
to 100% the memory usage rapidly increased to 400MB+, invoking a garbage collection manually
only brought it down to ~398MB. After a minute or so Karaf ran out of memory.  I'm attaching
a screenshot where you can see the point in cpu usage when I installed cellar-event, and it
looks like after maybe 2 seconds it takes a nosedive. The cellar multicast thread must have
some sort of memory leak  I can see if I can get any more details.  Below is the stacktrack
in the console when Karaf finally had enough:
> karaf@root>
> $ Exception in thread "qtp3198760-62" Exception in thread "hz._hzInstance_1_cellar.MulticastThread"
java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap
space
> java.lang.OutOfMemoryError: Java heap space
> karaf@root>
> Exception in thread "fileinstall-C:\Users\rmoquin\Downloads\apache-karaf-2.3.1/etc" Exception
in thread "Thread-29"     at java.io.BufferedOutputStream.<init>(Buffer
> edOutputStream.java:76)
> karaf@root>
> karaf@root>     at java.io.BufferedOutputStream.<init>(BufferedOutputStream.java:59)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:743)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:722)
> java.lang.OutOfMemoryError: Java heap space
>         at java.util.Arrays.copyOf(Arrays.java:2367)
>         at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
>         at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
>         at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
>         at java.lang.StringBuffer.append(StringBuffer.java:237)
>         at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.blackListHandler(EventHandlerProxy.java:431)
>         at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:167)
>         at org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:132)
>         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
>         at java.lang.Thread.run(Thread.java:722)
> java.lang.OutOfMemoryError: Java heap space
> 'org.apache.felix.eventadmin.impl.adapter.LogEventAdapter$1@81a259' is removed as a LogListener,
since it threw an exception.

--
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

Mime
View raw message