Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.3, 1.2.1, 1.3.0, 2.0.0
    • Fix Version/s: 1.0.4, 1.2.2, 1.3.0, 2.0.0-M3
    • Component/s: None
    • Labels:
      None

      Activity

      Hide
      Michael Dick added a comment -

      The values in the profile might not work well on trunk (I haven't tried) - they should be good for earlier releases (1.0.x).

      The earlier releases do not include an extensive lock manager test suite. The lock manager test suite is sensitive to these settings and has been known to cause problems with deadlockTimeout=5, waitTimeout=6.

      Some experimentation (without local changes) is advised before changing them in your environment (YMMV).

      Show
      Michael Dick added a comment - The values in the profile might not work well on trunk (I haven't tried) - they should be good for earlier releases (1.0.x). The earlier releases do not include an extensive lock manager test suite. The lock manager test suite is sensitive to these settings and has been known to cause problems with deadlockTimeout=5, waitTimeout=6. Some experimentation (without local changes) is advised before changing them in your environment (YMMV).
      Hide
      Michael Dick added a comment -

      Currently trunk uses the default derby.locks.waitTimeout (60) and a derby.locks.deadlockTimeout of 5. I suspect that these can be tuned for the developer's hardware and provide quicker test execution.

      <anecdotal evidence>
      setting waitTimeout = 10 saved me 5 - 10 minutes on a build last night.
      </anecdotal evidence>

      The properties can be specified on the command line :
      $ mvn -Dderby.locks.deadlockTimeout=10 -Dderby.locks.waitTimeout=15 clean test

      or in settings.xml :
      <profile>
      <id>derby-locking</id>
      <properties>
      <derby.locks.deadlockTimeout>3</derby.locks.deadlockTimeout>
      <derby.locks.waitTimeout>5</derby.locks.waitTimeout>
      </properties>
      </profile>

      The profile (as shown) needs to be activated on the command line :
      $ mvn -Pderby-locking clean test

      Show
      Michael Dick added a comment - Currently trunk uses the default derby.locks.waitTimeout (60) and a derby.locks.deadlockTimeout of 5. I suspect that these can be tuned for the developer's hardware and provide quicker test execution. <anecdotal evidence> setting waitTimeout = 10 saved me 5 - 10 minutes on a build last night. </anecdotal evidence> The properties can be specified on the command line : $ mvn -Dderby.locks.deadlockTimeout=10 -Dderby.locks.waitTimeout=15 clean test or in settings.xml : <profile> <id>derby-locking</id> <properties> <derby.locks.deadlockTimeout>3</derby.locks.deadlockTimeout> <derby.locks.waitTimeout>5</derby.locks.waitTimeout> </properties> </profile> The profile (as shown) needs to be activated on the command line : $ mvn -Pderby-locking clean test

        People

        • Assignee:
          Michael Dick
          Reporter:
          Michael Dick
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development