This page details possible items for implementation on the Access server.

• Distributed lock manager occasionally has file stores fail because “item not locked for read”
• A server (Production-A, I think) fell over on October 17, 2018 with “too many open files” exceptions. No idea why this happened.

• To make Project archiving more reliable tag various entities with UUID values (instead of just handles)
  • Projects
  • Vehicles
  • Tracks
  • more?
  • Add corresponding API methods to be able to retrieve entity by UUID value.
• Remove old Proxool DB connection pool, Hikari has proven successful. Proxool is not needed for fall back any longer.
• Move to JDK-11
  • Will require module support
• Move to OpenJDK instead of Oracle JDK
  • Oracle has introduced new licensing that makes it impossible to use moving forward.
• Implement a proper license use ledger table in DB
  • Ledger to have single row for checkout through checkin time
  • Fix usage reports to go to ledger
  • Reports will be more repeatable using ledger
  • Usage ledger can remain populated even for “killed” keys because the table refers to past use, not current activity.
• Implement simple AppLog table.
  • Apps (desktop mostly) will be able to log debug lines etc.
  • May need to build access tools for this (internal only, of course)
  • Removes cruft for the licenseLog table, which could slow down the checkin/out process
• Token generation should be “salted” so two different users with the same password will not create the same token.
• Add something to stored files so the web app can determine a public link before it's created. This is needed so the web app can paste the public link URL to the clipboard on the onClick() handler in the web app (it's a browser security limitation)
• Further generalization of the Job concept
  • Abstract jobs so pure linux machines can run them as extra processes but AWS severs could kick of Lambda jobs.