From dev-return-11673-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Mon May 04 16:40:55 2009 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 53146 invoked from network); 4 May 2009 16:40:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 May 2009 16:40:55 -0000 Received: (qmail 69699 invoked by uid 500); 4 May 2009 16:40:55 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 69645 invoked by uid 500); 4 May 2009 16:40:55 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 69635 invoked by uid 99); 4 May 2009 16:40:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 16:40:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.218.171 as permitted sender) Received: from [209.85.218.171] (HELO mail-bw0-f171.google.com) (209.85.218.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 16:40:47 +0000 Received: by bwz19 with SMTP id 19so3832568bwz.9 for ; Mon, 04 May 2009 09:40:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=iDb06FiexT9mVHfxZfaJiMt4abl7RGP6u3WFmiDC6SA=; b=BVw0u8pHFVzIb2udIuVLYQ7Ij0J4j+cuhgdlZVRYj63SmFllR7IbyguJDFiv91bjBB WpREQCE4aK70YoaBXqjkslhuTWoo7LGgrGtGEf3WSs/Nz/6akvejVfddkBuBUX3ZcgzE 9pKg7pMwtYpCuVBAkmdAkGEUjkfD+QqCtJpXw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=O3rae24enYHgYP5cK8FkzeV/6ljF3Ge6w9SgqTdzRG2pyxfoeJXU4a1WGCsbF/wEw/ e7LSKxTkTCeDDkLqRoOJo31SbwwAFr76CZwSCY0STark7dUQqbdQOhbLYYxhmzpAK4HD arrk8PSpfim0n7HMD436GDSwBWt/U2OoZ2OvA= MIME-Version: 1.0 Received: by 10.223.111.134 with SMTP id s6mr2342194fap.60.1241455225568; Mon, 04 May 2009 09:40:25 -0700 (PDT) In-Reply-To: <49FF182B.7010906@apache.org> References: <49FF182B.7010906@apache.org> Date: Mon, 4 May 2009 11:40:25 -0500 Message-ID: <72c1350f0905040940i6a483fd7rbc08085eb2b270cf@mail.gmail.com> Subject: Re: Stale input streams, take two From: Michael Dick To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=001636c5a501b98074046918d13b X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a501b98074046918d13b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Simone, What happens if you flush the change manually and then close the stream? It wouldn't be ideal, but it might avoid the other problems you're seeing. -mike On Mon, May 4, 2009 at 11:30 AM, Simone Gianni wrote: > Hi all again, > the previous thread on this subject died, so I'm bringing it up again. The > question is still how to close the input stream an application gives to > OpenJPA streaming lob support, since OpenJPA requires that stream to be open > until it flushes it to the database, which potentially happens outside the > application scope. > > Which is the listener that should be used to close those streams? Otherwise > how to close it at the right moment to prevent stale streams and errors in > OpenJPA? > > Simone > > -- > Simone Gianni CEO Semeru s.r.l. Apache Committer > http://www.simonegianni.it/ > > --001636c5a501b98074046918d13b--