#138 Incorrect timestamp

closed-accepted
None
3
2010-07-02
2010-04-27
calem
No

Hello guys!

I'm so sorry to bother you..
Just wanted to report a bug in Timestamp. My system's Timezone is GMT+8 where Jtrac was installed. But Jtrac seems getting a different Timezone. You may see the attached file for more reference...

Hoping for your soonest response..

Best regards,
Calem

Discussion

  • calem

    calem - 2010-04-27
     
  • Manfred Wolff

    Manfred Wolff - 2010-05-11
    • priority: 5 --> 3
    • assigned_to: nobody --> manfredwolff
    • status: open --> open-accepted
     
  • Manfred Wolff

    Manfred Wolff - 2010-05-11

    Hi Calem.

    I need some further informations:
    The system of the screenshot, is this the same as your server and your database or is the database on a different system ?

    Please provide more informations:
    - Servlet engine e.g. jetty, tomcat, glashfish with current version
    - database system eg. oracle, mysql, embedded hsql
    - system environment: On which maschine is which application.

    regards
    Manfred

     
  • calem

    calem - 2010-05-11

    Hi Sir manfredwolff,

    Thanks a lot for looking into my concern. And my apology for giving you incomplete info.
    I was accessing the Jtrac application into a different system but my workstation and the Jtrac server (where I installed the Jtrac), was synchronized in our NTP server. Please see below system environment where I installed Jtrac.

    OS: FreeBSD8 Stable
    JAVA: Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02)
    Servlet: Apache Tomcat 6.0.24 (localhost)
    Database: mysql-server-6.0.11 (localhost)

    I've set my Tomcat in my timezone = Asia/Manila by editing tomcat start-up script using CATALINA_OPTS & JAVA_OPTS but I still have no luck.

    My assumption (and not so sure of it) is that, Jtrac is not compatible with Tomcat version I'm using. Because the directory structure of Tomcat 5.5.28 is different from Tomcat6.x like for example the lib directory and etc. was different. I hope my assumption is correct. I'll try to downgrade my Tomcat version and see if it'll work. I'll let you know about the status.

    Thanks again for looking into my concern. More power to all developers!

    Regards,
    Calem

     
  • Manfred Wolff

    Manfred Wolff - 2010-05-12

    I don't thing that's really an issue of tomcat. I use tomcat (my current Timezone is +1) and I have got no problem with the timestamp.

    This might be a problem of the infrastructure. (Server, database). One of the system converts the time into UTC. Sorry, but in the moment I've no idea how I might help you.

     
  • calem

    calem - 2010-05-12

    Hi Sir manfredwolff,

    Thanks a lot for your time and effort and that's okay, I really understand your situation as the most active contributor in Jtrac at this moment in time.. :D
    I don't know if you'll believe in this, and I'm not saying that you are wrong. I've downgraded my tomcat version from tomcat 6.0.14 to tomcat 5.5.28 and it works fine now, in getting the right time stamp.. At first, I really don't think it will work though.. :D
    What makes me assume that the problem is with the tomcat version is because I have another web application built in php and running in Apache in the same server & database where Jtrac was setup, but it gets the correct time stamp.
    Although it's working now, but downgrading servlet I believe is not a resolution to this problem. Maybe I'll do some other workaround to see the root cause of the problem.

    Best regards and more power,

    Calem

     
  • Manfred Wolff

    Manfred Wolff - 2010-05-17

    Hi Calem.

    Strange ;-). I'm using Tomcat 6.0.18 and the problem does not occure. If a have a little time I will try out 6.0.14 if I can reproduce the problem. Perhaps it is a solution for you to upgrade to the newest tomcat version.

     
  • calem

    calem - 2010-05-17

    Hi Sir manfredwolff,

    Yeah, correct! I also called the help from our developers and have seen this resolution a bit strange.. : )
    Their conclusion is that, maybe from previous setup, JAVA_HOME, and CATALINA_HOME was not properly setup in environment causing Jtrac to confuse where to get time stamps or something like that. Now we will produce that error again to see the root cause. I'm building a server now and let you know what we've found..

    Thank you so much for your extensive support, and I'm really sorry to bother you.. :D

    Best regards,

    Calem

     
  • Manfred Wolff

    Manfred Wolff - 2010-05-17

    Hi Calem.

    No problem, you don't bother me !

    I've set up a Tomcat 6.0.14 and it works in my environment. If you have a solution for this problem please provide. In the moment I can nothing do for you, unfortunately.

    Regards
    Manfred

     
  • calem

    calem - 2010-07-02

    Hi Sir manfred,

    Sorry for late update, I was so busy the last few weeks. I've replicated the error and it was successful. Please see my system info below:

    OS: Freebsd 7.2 Stable
    Servlet: tomcat-5.5.28_1
    Java: diablo-jdk-1.6.0.07.02_9

    What I did to replicate the error in Time stamp was to improperly setup Tomcat by not setting the CATALINA_HOME & JAVA_HOME. And to resolve the problem is just to set it up properly. Strange.... : /

    What makes me crazy is that when I use tomcat-41, I never encounter this problem even though I never set up the CATALINA_HOME & JAVA_HOME.

    If you have idea why this strange problem appears between the 2 Tomcat version, please do share it co'z I really love to know the cause of this problem... It makes me crazy.... :D
    As of now, issue is already resolved.

    Anyways, many thanks for your kindest, extensive assistance and more power to you!

    Cheers!

    Calem

     
  • calem

    calem - 2010-07-02
    • status: open-accepted --> closed-accepted
     

Log in to post a comment.