Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So I have a strange problem, I have a java swing application that has the date 10/11/1922 00:00:00 MST but when it sends that date to my backend glassfish server via RMI the date becomes 10/10/1922 23:00:00 MST. So it is somehow losing an hour, is this a bug? I can’t find anything on google that references this problem. If I do a date in 1923 it works fine I don’t lose an hour. My client is running 1.6.0 patch 30 and my server is running 1.6.0 patch 17.
I think I’ve seen a question like this before–essentially there was a shift in the definition of timezones at that point in history, or something like that, so that hour actually never existed. I think, in fact, Jon Skeet was the one to locate the error (in the previous SO question). I can’t find it right now, I have to go to lunch, but I think it’s out there 😀