Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with spring config and merge policies #488

olarivain opened this issue May 28, 2013 · 0 comments


None yet
2 participants
Copy link

commented May 28, 2013


I was trying to setup the wan replication on a distributed map running a Jersey/Spring server, and kept getting "no merge policies defined" severe error in the logs whenever the replication kicked in. And, sure thing, my nodes were not replicating themselves, confirmed by breakpointing and reading from the maps directly.

The config was pretty much copy/paste from the spring config doc:

<hz:map ...>
    <hz:wan-replication-ref name="replicated-cluster"
                    merge-policy="hz.PASS_THROUGH" />

Digging some more, I found CMap.getMergePolicy(String) ends up always returning null:

The node's config always has an empty Map for the mergePolicyConfig attribute, at least when going with the default, out of the box, spring configuration.
Putting a breakpoint in Config.setMergePolicyConfigs(Map), I indeed get a call, apparently from Spring's context factory, setting the field to an empty map.

Eclipse is acting up on me and bluntly refusing to attach jar sources when debugging, so I didn't go much further than that, my best guess here is that the HazelcastConfigBeanDefinitionParser is wrongfully assigning an empty merge policy config when no merge-policies tag is present, effectively overriding the implicit, hardcoded default values in Config's default constructor.

The result is that CMap.getMergePolicy(String) always returns null, for all merge policies, even the default ones (hz.LATEST_UPDATE, hz.PASS_THROUGH, etc.). This affects the wan replication, but also the map's merge policy, which sounds like a big problem.

I confirmed this with hazelcast 2.4.1 and 2.5.1, using the maven artifacts.

The workaround I've found is to explicitly define the merge policies beans used by the map/wan-replication, give them custom names and refer to those in the config rather than the default names, for instance:

<bean id="otPassThroughMergePolicy" class="com.hazelcast.merge.PassThroughMergePolicy" />
<bean id="otLatestUpdateMergePolicy" class="com.hazelcast.merge.LatestUpdateMergePolicy" />

<hz:hazelcast id="hazelcast">
        <hz:map ...>
            <hz:wan-replication-ref name="replicated-cluster"
                    merge-policy="ot.PASS_THROUGH" />

            <hz:map-merge-policy name="ot.PASS_THROUGH"
                implementation="otPassThroughMergePolicy" />
            <hz:map-merge-policy name="ot.LATEST_UPDATE"
                implementation="otLatestUpdateMergePolicy" />

@ghost ghost assigned mdogan May 28, 2013

@mdogan mdogan closed this in 13672ee May 28, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.