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.

Sign up for GitHub

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

Jump to bottom

Cache event listeners triggers multiple events when the listener is configured using the xml #9315

Closed
ihsandemir opened this issue Nov 25, 2016 · 1 comment
Closed

Cache event listeners triggers multiple events when the listener is configured using the xml #9315

ihsandemir opened this issue Nov 25, 2016 · 1 comment
Assignees
@ihsandemir
Labels
Source: Internal PR or issue was opened by an employee Team: Client
Milestone
3.7.4

Comments

@ihsandemir
Copy link
Contributor

ihsandemir commented Nov 25, 2016 •
edited

When we create an EventListener to log on events such as create, update, expire, etc.. , and when we restart the client by keeping the server in place, for the first client start we see one printout for the first hit to an event, and when we restart the client we see two printouts for the second event, and when we restart the client again we see four for the third event, eight for the fourth, and so on.

This happens when listener is configured using the xml:

    <cache name="entrylistenertestcache">
        <expiry-policy-factory>
            <timed-expiry-policy-factory expiry-policy-type="CREATED" duration-amount="1" time-unit="SECONDS"/>
        </expiry-policy-factory>
        <cache-entry-listeners>
            <cache-entry-listener old-value-required="false" synchronous="false">
                <cache-entry-listener-factory class-name="com.hazelcast.client.cache.CacheEntryListenerTestFactory"/>
            </cache-entry-listener>
        </cache-entry-listeners>
    </cache>
@ihsandemir ihsandemir added this to the 3.7.4 milestone Nov 25, 2016
@ihsandemir ihsandemir self-assigned this Nov 25, 2016
@ihsandemir ihsandemir mentioned this issue Nov 25, 2016
Merged
ihsandemir added a commit to ihsandemir/hazelcast that referenced this issue Nov 25, 2016
@ihsandemir
Forward port of hazelcast#9233
a65e83f 
Fixes the issue of duplicating the cache config listener registration configurations (hazelcast#9315 ) when xml based listener is defined for a Cache. A new test is added as well.
@ihsandemir ihsandemir mentioned this issue Nov 25, 2016
Merged
ihsandemir added a commit that referenced this issue Nov 25, 2016
@ihsandemir
Cache event listeners triggers multiple events when the listener is c…
62c8ee7 
…onfigured using the xml - Forward #9233 (#9316)

* Forward port of #9233

Fixes the issue of duplicating the cache config listener registration configurations (#9315 ) when xml based listener is defined for a Cache. A new test is added as well.
@sancar
Copy link
Contributor

sancar commented Nov 29, 2016

fixed by #9233 and #9316

@sancar sancar closed this as completed Nov 29, 2016
tkountis pushed a commit to tkountis/hazelcast that referenced this issue Nov 30, 2016
@ihsandemir @tkountis
Cache event listeners triggers multiple events when the listener is c…
b5602e8 
…onfigured using the xml - Forward hazelcast#9233 (hazelcast#9316)

* Forward port of hazelcast#9233

Fixes the issue of duplicating the cache config listener registration configurations (hazelcast#9315 ) when xml based listener is defined for a Cache. A new test is added as well.
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ihsandemir ihsandemir

Labels
Source: Internal PR or issue was opened by an employee Team: Client
Projects
None yet
Milestone
3.7.4
Development

No branches or pull requests
3 participants
@sancar @ihsandemir @mmedenjak