Uploaded image for project: 'Jalview'
  1. Jalview
  2. JAL-3544

Consistent logging from initiation to launch of Jalview

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.11.1, 2.11.1.0, 2.11.1.1
    • Fix Version/s: 2.11.2
    • Component/s: Dev and Dep, launcher
    • Labels:
      None

      Description

      Jalview launch involves getdown or jalview.bin.Launcher and finally jalview.bin.Jalview. Informationals and debug trace messages are needed for each process to report when jvmmemmax is triggered. Currently these are written to System.err/out in each process, and not reliably captured in a single place.

      Work to do:
      1. Regularise logging across getdown and jalview.bin.Launcher
      2. Provide informational message should report when the maximum memory setting parameter has been used to limit the amount of memory allocated to Jalview by the launcher.
      3. Provide debug level log messages to report full details of the memory setting algorithm so people can more easily debug what's going on for their situation.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              soares Ben Soares
              Reporter:
              jprocter Jim Procter
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: