karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Tran <dant...@gmail.com>
Subject Re: Ability to self restart karaf [WAS] Infamous permgen leak
Date Thu, 15 Dec 2011 17:18:52 GMT
Here are notes after playing with dev:restart:

  1. Permgen still leaks

  2. Works only in main karaf shell ( ie invoke bin/karaf ).  When I
ran it as a service via wrapper and use bin/client to assess karaf
shell, dev:restart kill my karaf.

So it seems we need a cold restart.

-D

On Thu, Dec 15, 2011 at 9:02 AM, Dan Tran <dantran@gmail.com> wrote:
> I am using 2.2.x, can I invoke dev:restart in my own bundle? any side
> affect on this since my bundle also get restart.
>
> Thanks
>
> -D
>
> On Thu, Dec 15, 2011 at 8:48 AM, Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
>> It's already possible:
>>
>> - in the console: dev:restart for 2.2.x version, system:restart for trunk
>> (3.0)
>> - for the MBean, it's in org.apache.karaf:type=dev in Karaf 2.2.x (restart()
>> operation), or org.apache.karaf:type=system in Karaf 3.0.0 (trunk, restart()
>> operation)
>>
>> Regards
>> JB
>>
>>
>> On 12/15/2011 05:39 PM, Dan Tran wrote:
>>>
>>> Looks like the permgen issue is here for a long time.  How about
>>> adding ability for karaf to restart itself ( Hudson, and eclipse can
>>> do this i think ). May be via webconsole, or JMX
>>>
>>> Eager to hear how we could implement such feature for karaf.
>>>
>>> -D
>>>
>>> ---------- Forwarded message ----------
>>> From: Dan Tran<dantran@gmail.com>
>>> Date: Thu, Dec 15, 2011 at 12:23 AM
>>> Subject: Re: Infamous permgen leak
>>> To: user@karaf.apache.org
>>>
>>>
>>> It is about feature to be loaded in and out of karaf dynamically.  So
>>> I guess is a known issue to 'java', karaf is not an exception :(
>>>
>>> Wonder if ACE can solve this issue
>>>
>>>
>>> -D
>>>
>>> On Thu, Dec 15, 2011 at 12:15 AM, Jean-Baptiste Onofré<jb@nanthrax.net>
>>>  wrote:
>>>>
>>>> Hi Dan,
>>>>
>>>> just to understand your issues:
>>>> - if you talk about the feature service itself, I'm agree that it
>>>> shouldn't
>>>> consume perm
>>>> - but the loaded classes (loaded by the feature service) consumes perm,
>>>> and
>>>> it's a normal behavior (it's exactly the same with on Tomcat with
>>>> hot-deployment for instance)
>>>>
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 12/15/2011 08:36 AM, Dan Tran wrote:
>>>>>
>>>>>
>>>>> Hello Karaf Team
>>>>>
>>>>> Each time I reinstall/update a feature at runtime, my karaf loses some
>>>>> permgen. Amount depending on number to classes I have.  Is there any
>>>>> one able to address this issue?
>>>>>
>>>>> Setting JVM to  -XX:+CMSPermGenSweepingEnabled
>>>>> -XX:+CMSClassUnloadingEnabled  doesnot help.
>>>>>
>>>>> -Dan
>>>>
>>>>
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com

Mime
View raw message