Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6215

derby.log grows enormously during StressMultiTest

    XMLWordPrintableJSON

    Details

      Description

      When running suites.All with sane jars, I've seen derby.log grow very big (over 4GB) during StressMultiTest. I don't see this when StressMultiTest is run separately, only when it runs as part of suites.All.

      What takes the most space in derby.log is debug output like this

      DEBUG DaemonTrace OUTPUT: Next urgent assignment : org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
      DEBUG DaemonTrace OUTPUT: servicing org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
      DEBUG DaemonTrace OUTPUT: done org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
      DEBUG DaemonTrace OUTPUT: come back from yield

      repeated over and over.

      I suspect there's a test that sets the DaemonTrace debug flag, and that the flag for some reason doesn't get reset. I've only found one test that sets it: ClobReclamationTest. It uses a SystemPropertyTestSetup ensure the derby.debug.true property is reset and the engine rebooted, but I'm not sure rebooting the engine will reset the state of the SanityManager.

        Attachments

        1. derby-6215-01-a.diff
          3 kB
          Knut Anders Hatlen

          Activity

            People

            • Assignee:
              knutanders Knut Anders Hatlen
              Reporter:
              knutanders Knut Anders Hatlen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: