Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
Tested in Chrome 48.0.2564.109 m
*Location*: https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/#transactions-in-applied-state
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36
*Referrer*: https://www.google.ca/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/perform-two-phase-commits
Tested in Chrome 48.0.2564.109 m *Location*: https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/#transactions-in-applied-state *User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 *Referrer*: https://www.google.ca/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/perform-two-phase-commits
-
0.2
Description
The second example under the Regarding Multiple Applications header has a bug when getting the dateThreshold.
When new Date() returns a date which has a minutes value less than 30, setMinutes() is called with a negative value and as a result the date is invalidated.
The proper way to get dateThreshold is as follows:
var dateThreshold = new Date(); |
dateThreshold = new Date(dateThreshold.getTime() - 30*60*1000) |