Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F308796A0 for ; Tue, 21 Feb 2012 18:35:20 +0000 (UTC) Received: (qmail 95606 invoked by uid 500); 21 Feb 2012 18:35:20 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 95573 invoked by uid 500); 21 Feb 2012 18:35:20 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 95565 invoked by uid 99); 21 Feb 2012 18:35:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 18:35:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of st.never@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-wi0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 18:35:13 +0000 Received: by wibhm9 with SMTP id hm9so4751307wib.31 for ; Tue, 21 Feb 2012 10:34:53 -0800 (PST) Received-SPF: pass (google.com: domain of st.never@gmail.com designates 10.180.80.35 as permitted sender) client-ip=10.180.80.35; Authentication-Results: mr.google.com; spf=pass (google.com: domain of st.never@gmail.com designates 10.180.80.35 as permitted sender) smtp.mail=st.never@gmail.com; dkim=pass header.i=st.never@gmail.com Received: from mr.google.com ([10.180.80.35]) by 10.180.80.35 with SMTP id o3mr28377689wix.5.1329849293310 (num_hops = 1); Tue, 21 Feb 2012 10:34:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Q22+zZRZZe6VGI+3FEwSstfmdQS6ISttmQkUzwTXLYo=; b=UKz6iR145EE5RH6kqXAPsHzbbgrWAA3PEFkmUwkPmzC6fcoTC7hnC9nyEwY45szojK ckovOqINdtzKamukFtyOPj8a2sOOrrVhobLvgYqjE5rienlgOyicev1gg4VigKGCLelm gRYTSW7Oo3hjcz4TzKBNm1MDYQS95wgJMpK2U= MIME-Version: 1.0 Received: by 10.180.80.35 with SMTP id o3mr23616300wix.5.1329849293248; Tue, 21 Feb 2012 10:34:53 -0800 (PST) Received: by 10.216.63.130 with HTTP; Tue, 21 Feb 2012 10:34:53 -0800 (PST) Received: by 10.216.63.130 with HTTP; Tue, 21 Feb 2012 10:34:53 -0800 (PST) Date: Tue, 21 Feb 2012 16:34:53 -0200 Message-ID: Subject: Re: Shutdown DB does not work / threadding issue From: =?ISO-8859-1?Q?Jos=E9_Ventura?= To: Derby Discussion Content-Type: multipart/alternative; boundary=f46d044287f2ba993104b97daa7f X-Virus-Checked: Checked by ClamAV on apache.org --f46d044287f2ba993104b97daa7f Content-Type: text/plain; charset=ISO-8859-1 Try calling .join() on the thread object you created to run your Runnable. This will make the current thread wait until the child has finished. I forgot the reason why is solves the problem, it must be in the Java concurrency tutorials somewhere. On Feb 21, 2012 4:26 PM, "Karl Weber" wrote: --f46d044287f2ba993104b97daa7f Content-Type: text/html; charset=ISO-8859-1

Try calling .join() on the thread object you created to run your Runnable. This will make the current thread wait until the child has finished. I forgot the reason why is solves the problem, it must be in the Java concurrency tutorials somewhere.

On Feb 21, 2012 4:26 PM, "Karl Weber" <karl.weber99@googlemail.com> wrote:
--f46d044287f2ba993104b97daa7f--