subjectcache filename not unique per component

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: 2.4.0
    • Component/s: subject API
    • None
    • Environment:
      TIER package

      As discussed at Global Summit and on the TIER-GROUPER slack channel - multiple components running on the same host (with the same subject.properties) are colliding on the same cache filename.

      grouperSubjectCache__2019_03_04_08_54_41_027

      running daemon and ui on the same host cause them to use the same filename pattern as noted above.

      additionally, the writing of the file is performed as a quartz low priority and it really should be a high-priority, please.

            Assignee:
            Chris Hyzer (upenn.edu)
            Reporter:
            Michael Gettes (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: