Alex_Pastuhov
Legendary Poster
Thought I'd give an advanced warning - this may help someone:
The latest JDE tools releases (as well as all the corresponding JAS servers) are shipped with an older release of Java (1.5.0.5 or 1.5.0.6), but they also support W2008.
And as it turns out, these Java versions have an issue with the way W2008 timezone data is now stored in the registry, so in effect, the WEB server cannot find what it's after and quietly assumes it's GMT.
The end result is that whatever the WEB users do, all auditing fields show incorrect date/time.
After investigating this issue all around, we figured that a Java update is in order and it did indeed fixed this issue, once we upgraded it to 1.5.0.22.
The same, of course, applies to SM. Where it's limited to just the incorrect log timestamps, but even that is a bit annoying.
Now, fingers crossed, we are waiting to see what this change may have broken. Because naturally, this is the core engine behind the JAS and a slightest issue there may turn out to become a major problem with the system.
We have probably not been the first to come across this and surely will not be the last. Perhaps the future tools releases may come with a good version of Java, but until then, beware that this is something you will likely have to fix...
The latest JDE tools releases (as well as all the corresponding JAS servers) are shipped with an older release of Java (1.5.0.5 or 1.5.0.6), but they also support W2008.
And as it turns out, these Java versions have an issue with the way W2008 timezone data is now stored in the registry, so in effect, the WEB server cannot find what it's after and quietly assumes it's GMT.
The end result is that whatever the WEB users do, all auditing fields show incorrect date/time.
After investigating this issue all around, we figured that a Java update is in order and it did indeed fixed this issue, once we upgraded it to 1.5.0.22.
The same, of course, applies to SM. Where it's limited to just the incorrect log timestamps, but even that is a bit annoying.
Now, fingers crossed, we are waiting to see what this change may have broken. Because naturally, this is the core engine behind the JAS and a slightest issue there may turn out to become a major problem with the system.
We have probably not been the first to come across this and surely will not be the last. Perhaps the future tools releases may come with a good version of Java, but until then, beware that this is something you will likely have to fix...