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.
What happens if #setDefault(TimeZone timezone) is called by a concurrent application running on the same application server with JDK 1.6
As discussed in TimeZone #setDefault changes in JDK 6 the call now changes VM wide, this can have horrible consequences.
If you’re not adminsitrating the application server, how to ensure TimeZone doesn’t change?
My suggestion would be to ignore the default time zone completely. Always specify the time zone you want to use, making it a lot harder to accidentally use something that’s meaningful to you instead of the user. Indeed, for Noda Time we’ve removed everything that defaults the time zone.
Obligatory Joda reference: I’d also suggest using Joda Time instead of the built-in date/time APIs.