We have a use case where we trying to use felix in embedded mode. But we have a bunch of background jobs that run in parallel which initiate a new java process ending up accessing the same felix cache. And we are using the storage clean onFirstInit flag while starting the container. So in some scenarios when a race condition happens, on guy ends up deleting the cache, while other one things installation is successful and retrieval fails. What is the recommended pattern to solve this ? where we have 'n' java processes (n could be even 100+) , using embedded felix ?
Is using a unique felix-cache directory for each process good solution? do we run any risk. What are do and don't. In some cases some java processes may get killed abruptly. Re-using the same felix-cache without clean flag may get us into some issues as we see that felix stores some state information about bundles in the directory, so re-use may not be a good option. -- View this message in context: http://apache-felix.18485.x6.nabble.com/Suggested-solution-for-multiple-java-processes-accessing-felix-cache-in-embedded-more-tp5021145.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
