You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/04/09 19:31:50 UTC
[jira] Created: (OPENJPA-1624) Fix intermittent datacache timeout
failures in TestSJVMCache and CacheTest
Fix intermittent datacache timeout failures in TestSJVMCache and CacheTest
--------------------------------------------------------------------------
Key: OPENJPA-1624
URL: https://issues.apache.org/jira/browse/OPENJPA-1624
Project: OpenJPA
Issue Type: Bug
Components: jpa
Affects Versions: 2.0.0-beta3
Reporter: Donald Woods
Assignee: Donald Woods
Fix For: 2.0.0
We keep seeing intermittent failures in some of the datacache tests (mainly TestSJVMCache on DB2) due to how CacheTest uses hardcoded Thread.sleep() calls to try and time when the entities have been removed from the cache. Instead, I'm going to include some code to determine time elapsed, to make a better determination on how long to sleep. Also, will add some code to skip some of the cache checks when we've already passed the timeout value for the next entity, as sometimes the load on our DB2 machine affects these test runs (and the first couple of cacheCheck() calls almost always fail when running against a remote db server.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1624) Fix intermittent datacache timeout
failures in TestSJVMCache and CacheTest
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1624.
-----------------------------------
Resolution: Fixed
> Fix intermittent datacache timeout failures in TestSJVMCache and CacheTest
> --------------------------------------------------------------------------
>
> Key: OPENJPA-1624
> URL: https://issues.apache.org/jira/browse/OPENJPA-1624
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.0.0-beta3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1624.patch
>
>
> We keep seeing intermittent failures in some of the datacache tests (mainly TestSJVMCache on DB2) due to how CacheTest uses hardcoded Thread.sleep() calls to try and time when the entities have been removed from the cache. Instead, I'm going to include some code to determine time elapsed, to make a better determination on how long to sleep. Also, will add some code to skip some of the cache checks when we've already passed the timeout value for the next entity, as sometimes the load on our DB2 machine affects these test runs (and the first couple of cacheCheck() calls almost always fail when running against a remote db server.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENJPA-1624) Fix intermittent datacache timeout
failures in TestSJVMCache and CacheTest
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1624:
----------------------------------
Issue Type: Test (was: Bug)
> Fix intermittent datacache timeout failures in TestSJVMCache and CacheTest
> --------------------------------------------------------------------------
>
> Key: OPENJPA-1624
> URL: https://issues.apache.org/jira/browse/OPENJPA-1624
> Project: OpenJPA
> Issue Type: Test
> Components: jpa
> Affects Versions: 2.0.0-beta3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1624.patch
>
>
> We keep seeing intermittent failures in some of the datacache tests (mainly TestSJVMCache on DB2) due to how CacheTest uses hardcoded Thread.sleep() calls to try and time when the entities have been removed from the cache. Instead, I'm going to include some code to determine time elapsed, to make a better determination on how long to sleep. Also, will add some code to skip some of the cache checks when we've already passed the timeout value for the next entity, as sometimes the load on our DB2 machine affects these test runs (and the first couple of cacheCheck() calls almost always fail when running against a remote db server.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENJPA-1624) Fix intermittent datacache timeout
failures in TestSJVMCache and CacheTest
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1624:
----------------------------------
Attachment: OPENJPA-1624.patch
attaching patch for 2.0.x and trunk
> Fix intermittent datacache timeout failures in TestSJVMCache and CacheTest
> --------------------------------------------------------------------------
>
> Key: OPENJPA-1624
> URL: https://issues.apache.org/jira/browse/OPENJPA-1624
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.0.0-beta3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1624.patch
>
>
> We keep seeing intermittent failures in some of the datacache tests (mainly TestSJVMCache on DB2) due to how CacheTest uses hardcoded Thread.sleep() calls to try and time when the entities have been removed from the cache. Instead, I'm going to include some code to determine time elapsed, to make a better determination on how long to sleep. Also, will add some code to skip some of the cache checks when we've already passed the timeout value for the next entity, as sometimes the load on our DB2 machine affects these test runs (and the first couple of cacheCheck() calls almost always fail when running against a remote db server.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (OPENJPA-1624) Fix intermittent datacache
timeout failures in TestSJVMCache and CacheTest
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on OPENJPA-1624 started by Donald Woods.
> Fix intermittent datacache timeout failures in TestSJVMCache and CacheTest
> --------------------------------------------------------------------------
>
> Key: OPENJPA-1624
> URL: https://issues.apache.org/jira/browse/OPENJPA-1624
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.0.0-beta3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
>
> We keep seeing intermittent failures in some of the datacache tests (mainly TestSJVMCache on DB2) due to how CacheTest uses hardcoded Thread.sleep() calls to try and time when the entities have been removed from the cache. Instead, I'm going to include some code to determine time elapsed, to make a better determination on how long to sleep. Also, will add some code to skip some of the cache checks when we've already passed the timeout value for the next entity, as sometimes the load on our DB2 machine affects these test runs (and the first couple of cacheCheck() calls almost always fail when running against a remote db server.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.