Return-Path: 
 <users-return-8849-apmail-openjpa-users-archive=openjpa.apache.org@openjpa.apache.org>
X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org
Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6FE302D4C
	for <apmail-openjpa-users-archive@minotaur.apache.org>;
 Sat, 23 Apr 2011 02:49:57 +0000 (UTC)
Received: (qmail 34391 invoked by uid 500); 23 Apr 2011 02:49:57 -0000
Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org
Received: (qmail 34193 invoked by uid 500); 23 Apr 2011 02:49:56 -0000
Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@openjpa.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@openjpa.apache.org>
List-Post: <mailto:users@openjpa.apache.org>
List-Id: <users.openjpa.apache.org>
Reply-To: users@openjpa.apache.org
Delivered-To: mailing list users@openjpa.apache.org
Received: (qmail 34185 invoked by uid 99); 23 Apr 2011 02:49:55 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Apr 2011 02:49:55 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Apr 2011 02:49:50 +0000
Received: from jim.nabble.com ([192.168.236.80])
	by sam.nabble.com with esmtp (Exim 4.69)
	(envelope-from <ppoddar@apache.org>)
	id 1QDSuX-0002x1-CS
	for users@openjpa.apache.org; Fri, 22 Apr 2011 19:49:29 -0700
Date: Fri, 22 Apr 2011 19:49:29 -0700 (PDT)
From: Pinaki Poddar <ppoddar@apache.org>
To: users@openjpa.apache.org
Message-ID: <1303526969378-6298747.post@n2.nabble.com>
In-Reply-To: <1303407369225-6294995.post@n2.nabble.com>
References: <4DAF5A75.40702@gmail.com>
 <1303407369225-6294995.post@n2.nabble.com>
Subject: Re: Slice closing EntityManager on named queries
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Richard,
> Does Slice support JPQL queries? 
  Yes, it does. In fact, most of the testing is done on JPQL queries. 

  Can you experiemt with following choices:

  Expt 1. Replace the offending named query with the equivalent JPQL
directly. 
  Expt 2. Deactivate Prepared Query cache i.e. 
    <property name="openjpa.jdbc.QuerySQLCache" value="false"/>

  Let me know if you see any difference.

  I will see if I can reproduce the reported problem.

-----
Pinaki 
--
View this message in context: http://openjpa.208410.n2.nabble.com/Slice-closing-EntityManager-on-named-queries-tp6292434p6298747.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.