[DERBY-6215] derby.log grows enormously during StressMultiTest

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.8.3.3, 10.9.2.2, 10.10.2.0, 10.11.1.1
• Component/s: Test
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 08/May/13 11:10
• Updated: 16/Apr/14 02:41
• Resolved: 10/May/13 09:33

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.