Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <905624542.390951266597148054.JavaMail.jira@brutus.apache.org>
Date: Fri, 19 Feb 2010 16:32:28 +0000 (UTC)
From: "Donald Woods (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-1247) WriteBehindCallback sleepTime
 interval of one EMF datacache adversely impacting other EMF datacache
In-Reply-To: <222857844.1250320994823.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated OPENJPA-1247:
----------------------------------

    Patch Info:   (was: [Patch Available])
      Assignee:     (was: Donald Woods)

> WriteBehindCallback sleepTime interval of one EMF datacache adversely impacting other EMF datacache
> ---------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1247
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1247
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: writebehind
>    Affects Versions: 2.1.0
>            Reporter: Tim McConnell
>             Fix For: 2.1.0
>
>         Attachments: OPENJPA-1247.patch
>
>
> This problem surfaced when the WriteBehind configuration testcases introduced in OPENJPA-1237 caused the existing WriteBehind testcases in trunk to fail. Apparently, the WriteBehindCallback sleepTime interval of one EMF datacache is being used and adversely impacting other EMF datacaches. This is not the desired behavior as the WriteBehind datacache for each EMF should exist and function independently of any other WriteBehind datacache(s). The easiest way to demonstrate this failure is to increase the WriteBehindCallback sleepTime internval from 1000 to 15000 milliseconds in each of the testcases in TestWriteBehindConfigurations, as it will cause other WriteBehind testcases in trunk to fail. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.