ColdFusion time is wrong

[Dinghus]

This is on an old system that I am working on updating to CF8. Right now it is on a JRUN4 server with CFMX6.1

Today I got complaints that the time was wrong. I looked and sure enough CF is saying the time is 10 hours ahead of the server time. This suggests to me the GMT has gone to 0 since I'm in Hawaii with a GMT -10.

My question is, how do I change the GMT on the JRUN server?

[tooMuchTrouble]

http://forums.adobe.com/thread/552963?tstart=0

[Guest]

Dinghus - this is one of the many embarrassing situtation with CF product management. The first occurance of this issue can be found as way back as 2003. In other words since 8 years some of the fundamental requirements of a professional application server setting is still not fixed.  You can find endless discussions back and forth in the Internet - no real answer other than rebooting it after several changes, some complicated hacks or other absurd recommendation.

I'd consider it an 8 year old bug and hope it will be fixed once.

Axel

http://xeeme.com/AxelS

[Adam Cameron.]

Dinghus - this is one of the many embarrassing situtation with CF product management. The first occurance of this issue can be found as way back as 2003. In other words since 8 years some of the fundamental requirements of a professional application server setting is still not fixed.  You can find endless discussions back and forth in the Internet - no real answer other than rebooting it after several changes, some complicated hacks or other absurd recommendation.

I'd consider it an 8 year old bug and hope it will be fixed once.

Hang on.  Dingus is experiencing this on CFMX6.1 which was released in 2003 and has been end-of-lifed for years.  Do any of these endless discussions on Internet relate to still-supported versions of CF?  (not a rhetorical question).

And by the sounds of it, it's a Java issue, not specifically a CF one anyhow (based on Paul's response in the other thread), so your anguish is perhaps a bit misdirected in the first place.

--

Adam

[Guest]

@Adam - this is not an excuse but even worst as today version 9 has still the same issue. We just configured a few of those beasts and one just doesn't want to accept the server time. Now - is Adobe asking me to mess with the inner guts of the server to fix it? I know that many hackers love to those kind of "fixes" but not me. 

@Charlie - thanks for sharing the note. Tried it and failed as well.

I probably have to do the change time and restart several times, maybe shut down the entire server. But this is painful if you have a million users from around the world on it.

[Charlie Arehart]

To those complaining they find nothing addressing this, would you all count among that the Adobe technote addressing this specific issue, at least in one particular way:

http://kb2.adobe.com/cps/400/kb400888.html

That's not an attack, it's a sincere question. If it works, I hope Dingus will mark this reply as an "answer". If it doesn't work for others, let us know that, too.

I'll make one other observation: sometimes I see people say they made a needed change (to the jvm settings of CF Admin) and saw no benefit, but it was because they were changing the wrong admin/config. When running CF Enterprise in multiserver mode, note that each instance will have its own Admin, so be sure you're changing the right one. And while by default all instances share the same jvm.config, it is possible to configure things so each (or some) have their own jvm.config, which could also lead to a mistake in not applying the change to the right jvm.config. Just another thought to consider, if it may help.

[Adam Cameron.]

I'll make one other observation: sometimes I see people say they made a needed change (to the jvm settings of CF Admin) and saw no benefit, but it was because they were changing the wrong admin/config. When running CF Enterprise in multiserver mode, note that each instance will have its own Admin, so be sure you're changing the right one. And while by default all instances share the same jvm.config, it is possible to configure things so each (or some) have their own jvm.config, which could also lead to a mistake in not applying the change to the right jvm.config. Just another thought to consider, if it may help.

This is a good observation.  One way I check that I am editing the correct jvm.config file is to put something clearly wrong in the one I am editing, and try to start the CF instance.  If it doesn't start: I'm messing with the correct file 😉

--
Adam

[Charlie Arehart]

Yep, good one there, Adam.

/charlie