karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabian Lange <fabian.la...@codecentric.de>
Subject Re: Memory Leak in pax-url
Date Mon, 02 Nov 2015 17:24:02 GMT
This should "fix" it, right?

    System.setProperty("aether.updateCheckManager.sessionState", "bypass");

Fabian


On Mon, Nov 2, 2015 at 3:11 PM, Jean-Baptiste Onofré <jb@nanthrax.net>
wrote:

> Yes, I understand.
>
> I mean it's something to improve in Pax URL in order to use it in Karaf ;)
>
> Regards
> JB
>
>
> On 11/02/2015 03:08 PM, Fabian Lange wrote:
>
>> Hi JB,
>> unfortunately I cannot force that, I am using the pax url service behind
>> the scenes behind FeaturesService.
>>
>> Fabian
>>
>> On Mon, Nov 2, 2015 at 3:07 PM, Jean-Baptiste Onofré <jb@nanthrax.net>
>> wrote:
>>
>> Hi Fabian,
>>>
>>> I saw something similar in the Pax URL tests: for the SNAPSHOT, I used
>>> two
>>> different sessions in order to "force" the cache invalidation and
>>> retrieve
>>> the SNAPSHOT.
>>>
>>> It's something that we have to improve in Pax URL.
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/02/2015 02:59 PM, Fabian Lange wrote:
>>>
>>> Hi all,
>>>> there is a different issue with session caching.
>>>> "DefaultUpdateCheckManager        | 5 - org.ops4j.pax.url.mvn - 2.4.3 |
>>>> Skipped remote request for
>>>> group:artifact:1.0.0-SNAPSHOT/maven-metadata.xml, already updated during
>>>> this session."
>>>>
>>>> Any quick ideas how we could fix this?
>>>>
>>>> Fabian
>>>>
>>>> On Wed, Sep 23, 2015 at 4:05 PM, Fabian Lange <
>>>> fabian.lange@codecentric.de>
>>>> wrote:
>>>>
>>>> Great service, thank you!
>>>>
>>>>>
>>>>> Fabian
>>>>>
>>>>> On Wed, Sep 23, 2015 at 4:00 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>> >
>>>>> wrote:
>>>>>
>>>>> Hi guys,
>>>>>
>>>>>>
>>>>>> I will check the change, update to a Pax URL SNAPSHOT in Karaf (in
>>>>>> order
>>>>>> to test), do the release of Pax URL and include in Karaf ;)
>>>>>>
>>>>>> Let me create the Jira.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> On 09/23/2015 01:49 PM, Achim Nierbeck wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>>>
>>>>>>> procedure is simple, we would need a new release for Pax-URL
which
>>>>>>> will
>>>>>>> be
>>>>>>> included in the next version of Karaf 4.0.2,
>>>>>>> which is supposed to be released today ;)
>>>>>>> So we might just as well hold the release train for that for
another
>>>>>>> day
>>>>>>> to
>>>>>>> get Pax-URL released first.
>>>>>>>
>>>>>>> regards, Achim
>>>>>>>
>>>>>>> 2015-09-23 13:46 GMT+02:00 Fabian Lange <fabian.lange@codecentric.de
>>>>>>> >:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I found and fixed a memory leak in pax-url
>>>>>>>> https://github.com/ops4j/org.ops4j.pax.url/pull/16
>>>>>>>>
>>>>>>>> This crashed a couple of karaf instances I am running.
>>>>>>>>
>>>>>>>> I have not merged the fix yet (because I want some additional
eyes
>>>>>>>> on
>>>>>>>> it),
>>>>>>>> but I wonder how the procedure to get the fix into karaf
would be
>>>>>>>> then?
>>>>>>>> Could anybody support me here?
>>>>>>>>
>>>>>>>> Fabian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>> 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
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message