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

INT-4023: Fix MongoDB MGSs timing issue #1802

Merged
merged 1 commit into from May 6, 2016

Conversation

artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-4023

There is no guaranty that following System.currentTimeMillis() return the same value.
That is how the assertEquals() test for created and modified value may fail sporadically.

  • Fix MongoDbMessageStore and ConfigurableMongoDbMessageStore do not use a new System.currentTimeMillis()
    in case of group create

Cherry-pick to 4.2.x

JIRA: https://jira.spring.io/browse/INT-4023

There is no guaranty that following `System.currentTimeMillis()` return the same value.
That is how the `assertEquals()` test for `created` and `modified` value may fail sporadically.

* Fix `MongoDbMessageStore` and `ConfigurableMongoDbMessageStore` do not use a new `System.currentTimeMillis()`
in case of `group create`

**Cherry-pick to 4.2.x**
@garyrussell garyrussell merged commit 806bec3 into spring-projects:master May 6, 2016
@artembilan artembilan deleted the INT-4023 branch March 3, 2017 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants