I found the same problem as Vladimir Crnčić reported here. The last post in that thread was that one, where Dave Cramer said he cannot replicate the problematic behaviour. I cannot modify the example right now but I can say that this is happening when 'Europe/Madrid' timezone is used. As Vladimir said, I think the problem is in TimestampUtils.toTimestampBin() compensation.
PS: It is my first email here. My apologies if I have broken any protocol rule.