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 21:00:15 UTC

[jira] Commented: (OPENJPA-1210) Specify derby timeouts via properties.

    [ https://issues.apache.org/jira/browse/OPENJPA-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737232#action_12737232 ] 

Michael Dick commented on OPENJPA-1210:
---------------------------------------

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). 

> Specify derby timeouts via properties.
> --------------------------------------
>
>                 Key: OPENJPA-1210
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1210
>             Project: OpenJPA
>          Issue Type: Sub-task
>    Affects Versions: 1.0.3, 1.2.1, 1.3.0, 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>             Fix For: 1.0.4, 1.2.2, 1.3.0, 2.0.0
>
>   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.