Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-18230

Locale setting breaks build log timestamp

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 5.15.0.1
    • None

      Summary

      If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

      Environment

      Linux with locale settings that use special characters for either days or months.

      Steps to reproduce

      1. In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example: 
        JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=de -Duser.region=DE"

        We are now in March. In german, March is März. The "umlaut" cannot be parsed.

      2. Run a build.

      Expected results

      03-Mar-2017 16:33:55 	JOB1
03-Mar-2017 16:33:55 	going to sleep.
03-Mar-2017 16:33:58 	sleeping done

      Actual results

      01-Jan-1970 01:00:00 	JOB1
01-Jan-1970 01:00:00 	going to sleep.
01-Jan-1970 01:00:00 	sleeping done

      Workaround

      1. Force tomcat to use english locale: 
        JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"

            [BAM-18230] Locale setting breaks build log timestamp

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1765363 ] New: JAC Bug Workflow v3 [ 3384813 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Krystian Brazulewicz made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]
            Krystian Brazulewicz made changes -
            Link New: This issue duplicates BAM-14152 [ BAM-14152 ]
            Oleksandr Tkachenko made changes -
            Labels New: da-special-characters
            Patricio made changes -
            Description Original: h6. Summary
            If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

            h6. How to reproduce
            # In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=de -Duser.region=DE"
            {noformat}
            We are now in March. In german, March is März. The "umlaut" cannot be parsed.
            # Run a build. Output:
            {noformat}
            01-Jan-1970 01:00:00 JOB1
            01-Jan-1970 01:00:00 going to sleep.
            01-Jan-1970 01:00:00 sleeping done
            {noformat}

            h6. Workaround
            # Force tomcat to use english locale:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}

            h6. Expected output
            With the workaround this is the output:
            {noformat}
            03-Mar-2017 16:33:55 JOB1
            03-Mar-2017 16:33:55 going to sleep.
            03-Mar-2017 16:33:58 sleeping done
            {noformat}
            		New: h3. Summary
            If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

            h3. Environment
            Linux with locale settings that use special characters for either days or months.

            h3. Steps to reproduce
            # In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=de -Duser.region=DE"
            {noformat}
            We are now in March. In german, March is März. The "umlaut" cannot be parsed.
            # Run a build.

            h3. Expected results
            {noformat}
            03-Mar-2017 16:33:55 JOB1
            03-Mar-2017 16:33:55 going to sleep.
            03-Mar-2017 16:33:58 sleeping done
            {noformat}

            h3. Actual results
            {noformat}
            01-Jan-1970 01:00:00 JOB1
            01-Jan-1970 01:00:00 going to sleep.
            01-Jan-1970 01:00:00 sleeping done
            {noformat}

            h3. Workaround
            # Force tomcat to use english locale:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}


            Patricio made changes -
            Description Original: h6. Summary
            If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

            h6. How to reproduce
            # In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}
            We are now in March. In german, March is März. The "umlaut" cannot be parsed.
            # Run a build. Output:
            {noformat}
            01-Jan-1970 01:00:00 JOB1
            01-Jan-1970 01:00:00 going to sleep.
            01-Jan-1970 01:00:00 sleeping done
            {noformat}

            h6. Workaround
            # Force tomcat to use english locale:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}

            h6. Expected output
            With the workaround this is the output:
            {noformat}
            03-Mar-2017 16:33:55 JOB1
            03-Mar-2017 16:33:55 going to sleep.
            03-Mar-2017 16:33:58 sleeping done
            {noformat}
            		New: h6. Summary
            If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

            h6. How to reproduce
            # In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=de -Duser.region=DE"
            {noformat}
            We are now in March. In german, March is März. The "umlaut" cannot be parsed.
            # Run a build. Output:
            {noformat}
            01-Jan-1970 01:00:00 JOB1
            01-Jan-1970 01:00:00 going to sleep.
            01-Jan-1970 01:00:00 sleeping done
            {noformat}

            h6. Workaround
            # Force tomcat to use english locale:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}

            h6. Expected output
            With the workaround this is the output:
            {noformat}
            03-Mar-2017 16:33:55 JOB1
            03-Mar-2017 16:33:55 going to sleep.
            03-Mar-2017 16:33:58 sleeping done
            {noformat}
            Patricio made changes -
            Affects Version/s New: 5.15.0.1 [ 64338 ]
            Patricio made changes -
            Description New: h6. Summary
            If locale setting in the Bamboo Server computer makes the date use a special character, Bamboo will fail to parse the date, returning null.

            h6. How to reproduce
            # In catalina.sh (for Linux), add "user.language=XX" for JAVA_OPTS. For example:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}
            We are now in March. In german, March is März. The "umlaut" cannot be parsed.
            # Run a build. Output:
            {noformat}
            01-Jan-1970 01:00:00 JOB1
            01-Jan-1970 01:00:00 going to sleep.
            01-Jan-1970 01:00:00 sleeping done
            {noformat}

            h6. Workaround
            # Force tomcat to use english locale:
            {noformat}
            JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS -Duser.language=en -Duser.region=DE"
            {noformat}

            h6. Expected output
            With the workaround this is the output:
            {noformat}
            03-Mar-2017 16:33:55 JOB1
            03-Mar-2017 16:33:55 going to sleep.
            03-Mar-2017 16:33:58 sleeping done
            {noformat}
            Patricio created issue -

              Unassigned Unassigned
              pdemitrio Patricio
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: