Details

    • Type: Bug
    • Status: Closed
    • Priority: Default
    • Resolution: Fixed
    • Affects Version/s: 1.0.0 Final, 1.0.1, 1.0.2
    • Fix Version/s: 1.0.3
    • Component/s: Engine
    • Labels:
      None

      Description

      I may be wrong, but it seems that in the constructor for Session there's code that both accesses the incoming logFactory and also checks it for null, but not in the right order:

      constructor {
      Log log = logFactory.create(sessionID);

      try {
      <snip>
      if (logFactory != null)

      { state.setLog(log); }

      log.onEvent("Session " + this.sessionID + " schedule is " + sessionSchedule);
      }

      seems like if it's possible for the logFactory to be null, that assumption should be tested on the earlier line as wel.

        Attachments

          Activity

            People

            • Assignee:
              admin Steve Bate
              Reporter:
              toli Toli Kuznets
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: