I run Felix in Eclipse with a custom config.properties file that
autostarts a few bundles. If I include both org.apache.felix.log and
org.apache.felix.eventadmin in felix.auto.start.1, Felix hangs. If I
remove either org.apache.felix.log or org.apache.felix.eventadmin or
both, everything work
Short answer, no. At least not in the sense of truly "disabling the
bundle cache", because the mere fact that you want Felix to remember
that there are bundles in the cache to re-get means that it must be
saving something.
However, you can install a JAR file into the cache by reference using a
I would guess this is related to a deadlocking issue that was discussed
previously.
The issue is that Felix uses the external log service (if present) to
log events and sometimes this can lead to deadlocks, apparently. Of
course, this is just a guess on my part. I think there was a
workaround
This seems to be a common issue and I am also questioning the need to have a
cache.
Richard can you explain the rational behind the bundle cache and why it can't
be disabled?
Thanks
Patrick
-Original Message-
From: "Richard S. Hall" <[EMAIL PROTECTED]>
Sent: Saturday, March 22, 2008
Richard S. Hall wrote:
Short answer, no. At least not in the sense of truly "disabling the
bundle cache", because the mere fact that you want Felix to remember
that there are bundles in the cache to re-get means that it must be
saving something.
I may be missing something fundamental in how F
Thanks for the pointer.
It does appear to be the same problem as discussed here
(http://www.mail-archive.com/dev@felix.apache.org/msg03142.html). The
workaround of setting felix.log.level 3 (INFO) gets things working more
reliably.
In the message thread, Niclas Hedhman wondered if there are
