Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8797

HistoryCleanupHelper uses not thread safe SimpleDateFormat as class field

      The HistoryCleanupHelper has a
      SimpleDateFormat instance as class field which it uses unsynchronized.

      From the SimpleDateFormat docs:

      Date formats are not synchronized. It is recommended to create separate format instances for each thread. If multiple threads access a format concurrently, it must be synchronized externally.

      The SimpleDateFormat for example uses a calendar field which is modified during parsing of a date.

      AT:

      • the HistoryCleanupHelper uses the SimpleDateFormat in a thread safe way or a thread safe alternative

        This is the controller panel for Smart Panels app

            [CAM-8797] HistoryCleanupHelper uses not thread safe SimpleDateFormat as class field

            Roman Smirnov created issue -
            Roman Smirnov made changes -
            Labels New: SUPPORT
            Roman Smirnov made changes -
            Link New: This issue is depended on by SUPPORT-4104 [ SUPPORT-4104 ]
            Roman Smirnov made changes -
            Remote Link New: This issue links to "Page (camunda confluence)" [ 12008 ]
            Daniel Meyer made changes -
            Description Original: The [feel function mapper|https://github.com/camunda/camunda-engine-dmn/blob/28d4638eddd843de12f07dbb65590e2310f7acb4/feel-juel/src/main/java/org/camunda/bpm/dmn/feel/impl/juel/el/FeelFunctionMapper.java#L31] has a
            SimpleDateFormat instance as class field which it uses unsynchronized.

            From the SimpleDateFormat docs:
            {quote}Date formats are not synchronized. It is recommended to create separate format instances for each thread. If multiple threads access a format concurrently, it must be synchronized externally.{quote}

            The SimpleDateFormat for example uses a calendar field which is modified during parsing of a date.

            AT:
            - the HistoryCleanupHelper uses the SimpleDateFormat in a thread safe way or a thread safe alternative
            New: The HistoryCleanupHelper has a
            SimpleDateFormat instance as class field which it uses unsynchronized.

            From the SimpleDateFormat docs:
            {quote}Date formats are not synchronized. It is recommended to create separate format instances for each thread. If multiple threads access a format concurrently, it must be synchronized externally.{quote}

            The SimpleDateFormat for example uses a calendar field which is modified during parsing of a date.

            AT:
            - the HistoryCleanupHelper uses the SimpleDateFormat in a thread safe way or a thread safe alternative
            Roman Smirnov made changes -
            Assignee New: Roman Smirnov [ roman.smirnov ]
            Fabian made changes -
            Affects Version/s New: 7.9.0-alpha2 [ 15291 ]
            Roman Smirnov made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Roman Smirnov made changes -
            Assignee Original: Roman Smirnov [ roman.smirnov ] New: Nikola Koevski [ nikola.koevski ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Nikola Koevski made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              nikola.koevski Nikola Koevski
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: