The ManagedServiceFactory comes from a bundle right ?
It's a bundle containing a service implementing ManagedServiceFactory.
So, you have to sync the bundle with Cellar: you will have the factory
on the nodes, and the sync on the config created by the factory.
You see what I mean ?
Regards
JB
On 01/22/2015 07:36 PM, Ronny Bräunlich wrote:
Hi Jean-Baptiste,
I’m sure you didn’t exclude it just for fun :D
According to your example, node1 shares the configuration (without factoryPid)
with node2. Does node2 generate its own factoryPid then? Shouldn’t this result
in both ManagedFactories on both nodes creating a service?
I tried this before and it didn’t work.
Could I avoid this whole problem by providing the configuration via a bundle?
Cheers,
Ronny
Am 22.01.2015 um 19:19 schrieb Jean-Baptiste Onofré <[email protected]>:
Just one thing: even if factoryPid property is excluded, all other properties
are sync (so basically all the config). Only the factoryPid is local to the
node.
Let me explain:
- you have two nodes: node1 and node2 will have the config resulting from the
factory. factoryPid on config on node1 will be 231312867431cdqs23 and on node2 will
be 23131289SDSZé& (for instance ;)). But the config themselves will be
aligned/sync by Cellar.
So, you can have your factory on each node, and the config created by the
factory sync.
Do you see what I mean ?
I didn't excluded factoryPid property just for fun ;)
Regards
JB
On 01/22/2015 06:27 PM, Ronny Bräunlich wrote:
Hi everyone,
I am using Apache Karaf 3.0.2 and Cellar 3.0.1-SNAPSHOT (built from
commit 7a598b285f7b302efa15d9887dfea9d855b9951a) and I think I found a bug.
I have two Karaf instances running. On both I installed Cellar and this
simple project
https://github.com/rbraeunlich/karaf-managed-service-factory-example
After setting config.listener = true on both and removing
service.factoryPid from the config.excluded.properties I dropped a
config file into the etc/ directory.
Then I could see the factory on the first Karaf instance getting called
with the properties roughly every 100ms.
Debugging the Karaf couldn’t show me the source of the problem. I
suggest the Karaf updates itself and therefore calls the update() method
all the time.
The second instance didn’t make a move all the time.
Does anyone have a clue?
Cheers,
Ronny
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
