Hi
Am 25.09.2013 um 09:21 schrieb Rudolph, Dirk:
Thanks for your response.
The state of the bundle is ACTIVE. Unfortunately the original Exception
causing the previously attacked ISE isn't passed to the ISE itself and
therefore not in the stacktrace:
ERROR:
That's right. I also think the issue is related to FELIX-3067. Should I
describe the issue their again (just for completeness)?
We will split the bundles based on technology used.
Thanks a lot,
Dirk
-Ursprüngliche Nachricht-
Von: Felix Meschberger [mailto:fmesc...@adobe.com]
Hi
Am 25.09.2013 um 10:42 schrieb Rudolph, Dirk:
That's right. I also think the issue is related to FELIX-3067. Should I
describe the issue their again (just for completeness)?
Yes, that might be a good idea. And you also might want to attach the thread
dump
Regards
Felix
We will split
Hi :
Which classloader load Fragment(Fragment-Host: system.bundle;
extension:=framework), boot classloader?? or system classloader??
And how to trace loading class info?
gavin.yao
On 9/25/13 05:25 , gavin.yao wrote:
Hi :
Which classloader load Fragment(Fragment-Host: system.bundle;
extension:=framework), boot classloader?? or system classloader??
I believe this would be the class loader that loaded the framework
classes, which is typically the application class
Ok, done.
Splitting up the bundles didn't solve the issue for us...
The Blueprint Extender still can't acquire the bundle lock because global lock
is hold by another thread. So the reason of the bad restart behavior is the
weak cohesion of our application (when I redeploy nearly the whole
On Wed, Sep 25, 2013 at 1:39 PM, Rudolph, Dirk
dirk.rudo...@t-systems.comwrote:
Ok, done.
Splitting up the bundles didn't solve the issue for us...
The Blueprint Extender still can't acquire the bundle lock because global
lock is hold by another thread. So the reason of the bad restart
That's right ... it worked in the same application previously too. But after
adding scr to the bundle also containing blueprint the bug was triggered. I
agree with Felix M. that a week cohesion is the reason why it appears in our
application, indicated by the number of dependencies between the
Hello all,
First of all I'd like to say how wonderful iPOJO works. Thanks for all
the hard work going into that project (and all the others at Apache
Felix). (Most of the time) there's good warnings or errors on why a
requirement could not be fulfilled, also the messages when
configurations
On 9/25/13 10:59 , Debeerst Benjamin wrote:
Hello all,
First of all I'd like to say how wonderful iPOJO works. Thanks for all
the hard work going into that project (and all the others at Apache
Felix). (Most of the time) there's good warnings or errors on why a
requirement could not be
Roland, thank you so much for you help.
The problem was with the maven3 and it aparently fixed, like you can see it
here https://issues.apache.org/jira/browse/FELIX-3031 .
In my case I just needed to take out the SNAPSHOT word from the jar name.
--
View this message in context:
11 matches
Mail list logo