Yep. Talking about the data/cache. Again, we've seen a few cases where it seems our services have been picking up stale settings from previously deployed versions. We've also seen the same service configured as expected in one karaf instance, but behave differently when deployed in another. Which again, leads us to think there is possibly stale data in the karaf data cache. Not some something we've seen often, but definitely have seen it.
IMHO, "cache" is somewhat of a misnomer for karaf's data/cache in that typically I think of a cache as something that provides quick access to data that stored more durably somewhere else. In the case of the karaf cache, if you delete the cache, features that were installed via feature install command are effectively removed from karaf from what I can tell. More along the lines of what I'd expect is that I'd be able to delete the cache (if it gets corrupted for example) and then it'd be rebuilt from more durable storage, but that doesn't seem to be the case at least for features installed using the install command. I don't know the functionality for features installed via hot deploying to deploy folder. That may be more in line with what I'd expect. -e -- View this message in context: http://karaf.922171.n3.nabble.com/Cache-structure-tp4034630p4034640.html Sent from the Karaf - User mailing list archive at Nabble.com.
