Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.215.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKiEphJjb3v9Oeaf-d0LcszR1pDwKVZ4Q+6rV=zGdsu-SDpnRQ@mail.gmail.com>
References: 
 <CAKiEphJjb3v9Oeaf-d0LcszR1pDwKVZ4Q+6rV=zGdsu-SDpnRQ@mail.gmail.com>
From: Kevin Sutter <kwsutter@gmail.com>
Date: Tue, 28 May 2013 08:48:09 -0500
Message-ID: 
 <CABH8ermyuAs9jNGfrvW29o_N7fNAoP7WTMBG4pzB_nn5zxaxPw@mail.gmail.com>
Subject: Re: How to define a timeout for nativeQuery by OpenJPA 1.2.2
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=001a11c23f6432eb3f04ddc785cb

--001a11c23f6432eb3f04ddc785cb
Content-Type: text/plain; charset=ISO-8859-1

Hi Yu Wang,
I'm not clear on what you are trying to demonstrate.  The OpenJPA junit
bucket does have some tests for the various timeout hints and their usage
with finders and queries.  If you can further explain what your expected
results should be (via a junit?), it would be helpful.  Thanks,

Kevin


On Mon, May 27, 2013 at 1:12 AM, yu wang <wangyumi@gmail.com> wrote:

> *
> I found *
> *javax.persistence.query.timeout
>  does not work.
>
> query = manager.createNativeQuery(sql, Mybean.class);
>
>         query.setHint("openjpa.FetchPlan.LockTimeout", new Integer(30000));
>         query.setHint("javax.persistence.lock.timeout", new
> Integer(30000));
>         query.setHint("javax.persistence.query.timeout", new
> Integer(30000));
>
>         if (TsamLogger.isInfoEnabled(log)) {
>           start_time = System.currentTimeMillis();
>         }
>         reslist = query.getResultList();
>
> *
> *Regards,
> Yu Wang
> *
> **
>

--001a11c23f6432eb3f04ddc785cb--