You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2009/07/30 20:05:14 UTC
[jira] Updated: (OPENJPA-1210) Specify derby timeouts via
properties.
[ https://issues.apache.org/jira/browse/OPENJPA-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1210:
----------------------------------
Remaining Estimate: 0h
Original Estimate: 0h
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
> Specify derby timeouts via properties.
> --------------------------------------
>
> Key: OPENJPA-1210
> URL: https://issues.apache.org/jira/browse/OPENJPA-1210
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Michael Dick
> Assignee: Michael Dick
> Original Estimate: 0h
> Remaining Estimate: 0h
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (OPENJPA-1210) Specify derby timeouts via
properties.
Posted by Michael Dick <mi...@gmail.com>.
Hi Donald,
I didn't run trunk with those examples, I tried 5 and 10 though and it
worked.
When I added those comments I was thinking of the service releases which
don't have the lock manager tests (those values have worked for me in the
past). I'll add remarks to the JIRA to indicate that these are not safe
values for trunk at this moment.
Good catch though - I should have thought about trunk when I posted.
-mike
On Thu, Jul 30, 2009 at 1:16 PM, Donald Woods <dw...@apache.org> wrote:
> You ran the lockmgr and query.timeout tests under openjpa-persistence-jdbc
> with the derby-locking profile below? Most of the lockmgr and query timeout
> tests failed when I tried using waitTimeout=6 while working on
> OPENJPA-1071....
>
>
> -Donald
>
>
>
> Michael Dick (JIRA) wrote:
>
>> [
>> https://issues.apache.org/jira/browse/OPENJPA-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Michael Dick updated OPENJPA-1210:
>> ----------------------------------
>>
>> Remaining Estimate: 0h
>> Original Estimate: 0h
>>
>> 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
>>
>> Specify derby timeouts via properties.
>>> --------------------------------------
>>>
>>> Key: OPENJPA-1210
>>> URL: https://issues.apache.org/jira/browse/OPENJPA-1210
>>> Project: OpenJPA
>>> Issue Type: Sub-task
>>> Reporter: Michael Dick
>>> Assignee: Michael Dick
>>> Original Estimate: 0h
>>> Remaining Estimate: 0h
>>>
>>>
>>
>>
Re: [jira] Updated: (OPENJPA-1210) Specify derby timeouts via properties.
Posted by Donald Woods <dw...@apache.org>.
You ran the lockmgr and query.timeout tests under
openjpa-persistence-jdbc with the derby-locking profile below? Most of
the lockmgr and query timeout tests failed when I tried using
waitTimeout=6 while working on OPENJPA-1071....
-Donald
Michael Dick (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/OPENJPA-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Michael Dick updated OPENJPA-1210:
> ----------------------------------
>
> Remaining Estimate: 0h
> Original Estimate: 0h
>
> 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
>
>> Specify derby timeouts via properties.
>> --------------------------------------
>>
>> Key: OPENJPA-1210
>> URL: https://issues.apache.org/jira/browse/OPENJPA-1210
>> Project: OpenJPA
>> Issue Type: Sub-task
>> Reporter: Michael Dick
>> Assignee: Michael Dick
>> Original Estimate: 0h
>> Remaining Estimate: 0h
>>
>
>