Yes its still happen with latest karaf 2.3-1-SNAPSHOT. The good news
is not does not happen offen, i would say 5% compare to 50% with 2.3.0

-D

On Fri, Feb 8, 2013 at 11:27 PM, Jean-Baptiste Onofré <[email protected]> wrote:
> Hi Dan,
>
> with which version of Karaf do you see the issue ?
> Did you try with the latest 2.3.1-SNAPSHOT (including new Aries Blueprint) ?
>
> It looks like the issue that we had in Aries Blueprint in Karaf 2.3.0.
>
> Regards
> JB
>
>
> On 02/09/2013 03:02 AM, Dan Tran wrote:
>>
>> it is reproducible consistently on fast box ( 8 CPU modern development
>> box windows or linux )
>>
>> -D
>>
>> On Fri, Feb 8, 2013 at 9:17 AM, Dan Tran <[email protected]> wrote:
>>>
>>> Hi Lukasz
>>>
>>> [ 153] [Active     ] [            ] [   60] Wicket Util (6.2.0)
>>> [ 154] [Active     ] [            ] [   60] Wicket Request (6.2.0)
>>> [ 155] [Active     ] [            ] [   60] Wicket Core (6.2.0)
>>> [ 156] [Active     ] [            ] [   60] Wicket Auth Roles (6.2.0)
>>> [ 157] [Active     ] [            ] [   60] Wicket Extensions (6.2.0)
>>> [ 159] [Active     ] [            ] [   60] OPS4J Base - All (1.4.0)
>>> [ 160] [Active     ] [Created ] [   60] OPS4J Pax Wicket :: Service
>>> (2.0.0)
>>> [ 161] [Active     ] [            ] [   60] Apache ServiceMix ::
>>> Bundles :: cglib (2.2.2.1)
>>>
>>>
>>>
>>> Any more idea?
>>>
>>> -D
>>>
>>> On Fri, Feb 8, 2013 at 1:52 AM, Łukasz Dywicki <[email protected]>
>>> wrote:
>>>>
>>>> Hey Dan,
>>>> I did not experience this kind of problem. Have you tried if
>>>> org.ops4j.pax.wicket bundle is in ACTIVE state not RESOLVED?
>>>>
>>>> Cheers,
>>>> Lukasz
>>>>
>>>> Wiadomość napisana przez Dan Tran <[email protected]> w dniu 8 lut 2013,
>>>> o godz. 08:08:
>>>>
>>>>> by default, the bundle should bail out after 5 min, but it hangs that
>>>>> state forever. Sound like blueprint bug?
>>>>>
>>>>> I am using karaf 2.3.0 java 1.7
>>>>>
>>>>> -D
>>>>
>>>>
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Reply via email to