[
https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697773#action_12697773
]
Pierre De Rop commented on FELIX-1027:
--------------------------------------
Richard,
I reproduce the problem in a simpler way, without using the "Updater" bundle at
all. (yon can discard it).
Now, in my felix config, I just start bundle A, and B:
----------------------------------
felix.auto.start.1= \
file:bundle/org.apache.felix.shell-1.1.0-SNAPSHOT.jar \
file:bundle/org.apache.felix.shell.tui-1.1.0-SNAPSHOT.jar \
file:bundle/org.apache.felix.bundlerepository-1.3.0-SNAPSHOT.jar \
file:bundle/A.jar \
file:bundle/B.jar \
# don't activate felix debug ...
felix.log.level=1
---------------------------------------------------------------------------
and I start felix like this (I use jdk 1.5.0_18):
rm -rf felix-cache/;
java -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass -jar bin/felix.jar
-> B starting ...
java.lang.ClassNotFoundException: a.A
at
org.apache.felix.framework.searchpolicy.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:565)
at
org.apache.felix.framework.searchpolicy.ModuleImpl.access$100(ModuleImpl.java:59)
at
org.apache.felix.framework.searchpolicy.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at b.Legacy.run(Legacy.java:6)
at java.lang.Thread.run(Thread.java:595)
If you don't get the CNF, then manually stop/update/refresh/start bundle B,
like this, and you will probably get the CNF:
-> B starting ...
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (1.7.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (1.1.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (1.1.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository (1.3.0.SNAPSHOT)
[ 4] [Active ] [ 1] A (1.0.0)
[ 5] [Active ] [ 1] B (1.0.0)
-> stop 5
-> update 5
-> refresh 5
-> start 5
B starting ...
java.lang.ClassNotFoundException: a.A
at
org.apache.felix.framework.searchpolicy.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:565)
at
org.apache.felix.framework.searchpolicy.ModuleImpl.access$100(ModuleImpl.java:59)
at
org.apache.felix.framework.searchpolicy.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at b.Legacy.run(Legacy.java:6)
at java.lang.Thread.run(Thread.java:619)
> deadlock with felix 1.6.0 ?
> ---------------------------
>
> Key: FELIX-1027
> URL: https://issues.apache.org/jira/browse/FELIX-1027
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Environment: jdk1.5, linux
> Reporter: Pierre De Rop
> Priority: Critical
> Attachments: deadlock.txt,
> deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt,
> test-deadlock.tgz
>
>
> I just came across a deadlock with the felix 1.6.0 candidate version for the
> next fwk version.
> I have attached to this post the corresponding "kill -QUIT" output.
> Richard, is it really an framework deadlock ? This is strange because I am
> testing the trunk since one month and never noticed the problem ...
> /pierre
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
