Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Date: Mon, 10 Apr 2017 19:02:08 -0700 (MST)
From: jsaimani <jayanthsaimani@gmail.com>
To: users@felix.apache.org
Message-ID: <1491876128544-5021145.post@n6.nabble.com>
Subject: Suggested solution for multiple java processes accessing felix
 cache in embedded more
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 11 Apr 2017 02:03:03 -0000

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-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org