Hi Sahoo,
We probably need to create a felix-commands module. However, I am not
sure what you mean by "it needs to be run offline". For it to run
offline in a cluster case means administrator has to log on to a machine
where cluster instance runs, which is not always practical.
But I understand that you don't need a running server to delete felix-cache
when you are running in single instance case.
This needs some more thought, I believe ...
-Kedar
Sahoo wrote:
> Kedar,
>
> That definitely helps. Yes, we should have a command to clear the cache.
> It has to run offline.
>
> Thanks,
> Sahoo
>
> Kedar Mhaswade wrote:
>> Hi Sahoo,
>>
>> We can reuse this location in clustered setup since this is something
>> that first time server startup creates and subsequent runs reuse.
>> (Correct me if I am wrong).
>>
>> So, as long as you use ${com.sun.aas.instanceRoot}/felix-cache, we
>> should be okay in either case (single server, clusters).
>>
>> Note: instance file-layout (local configuration repository) mostly mimics
>> the domain folder.
>>
>> Hope this helps.
>>
>> -Kedar
>>
>> PS- We have to define a command to delete the cache when required.
>>
>> Sahoo wrote:
>>> Each OSGi framework requires a persistence location where it caches
>>> the state of the system for subsequent runs. Although, we can start
>>> with a clean cache everytime we start the server, the start up time
>>> reduces if the cache is reused. Currently we create the cache in
>>> domain_dir/felix-cache. I don't think I have made the correct choice
>>> as far as the location is concerned, because in a clustered set up,
>>> domain_dir is shared by multiple instances. I am looking for a
>>> location that's exclusively to an instance. Any hint what that is.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>