From dev-return-36199-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Wed Feb 18 17:40:37 2009 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 33911 invoked from network); 18 Feb 2009 17:40:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Feb 2009 17:40:37 -0000 Received: (qmail 82846 invoked by uid 500); 18 Feb 2009 17:40:36 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 82815 invoked by uid 500); 18 Feb 2009 17:40:36 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 82802 invoked by uid 99); 18 Feb 2009 17:40:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 09:40:36 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pmcfirst@gmail.com designates 72.14.220.152 as permitted sender) Received: from [72.14.220.152] (HELO fg-out-1718.google.com) (72.14.220.152) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 17:40:28 +0000 Received: by fg-out-1718.google.com with SMTP id l27so913816fgb.36 for ; Wed, 18 Feb 2009 09:40:07 -0800 (PST) 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 :content-transfer-encoding; bh=h0jS8TRPKX6uUlWvdN0YTxLe4IrQYVxAVE2A5+N7PuQ=; b=pPz7bUdz1BeIl4TyjIGhR/rujHHPpWgtL/VFUONiu89e49XzvysmrfLZOYFfUC8Vj0 nExlI3k7hyTSHiARkx0ZVdYPqo8JyVsI6gLPgjSKeQ7nTUmFoYngam/jLFSKqu936Byl MpBKeEWdZizF4Xq3Ji3fTbkHK0YG1By1fVFYA= 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:content-transfer-encoding; b=udgiveHeEBesCAlyefsxcg67yFBxKRSaFm+d9zUZUaasoWr+B3HFp3IFAi5+Vvf7pY 54h9hB7OJJG5RAChEYiQkrxGBHT3kc7qI98/Rt3I3/1aEf576AEINgmAnflXzwhRDHZ+ DSBDVZEyKPQwAxRCRAMcC8M2Q1hqeyaAtQCag= MIME-Version: 1.0 Received: by 10.103.171.20 with SMTP id y20mr4822999muo.122.1234978807228; Wed, 18 Feb 2009 09:40:07 -0800 (PST) In-Reply-To: <49970.69.157.206.34.1234972770.squirrel@email.powweb.com> References: <49970.69.157.206.34.1234972770.squirrel@email.powweb.com> Date: Wed, 18 Feb 2009 20:40:07 +0300 Message-ID: Subject: Re: Hello Pavel, inquiring about Harmony bug 5505 From: Pavel Pervov To: webmaster@quadmore.com, dev@harmony.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Bert, It is much more useful to write to Harmony dev-list, as you can attract more attention to your requests or problems. Unfortunately, I had no chance of working on HARMONY-5505 once I've submitted the work-in-progress patch for it. Are you planning to use radar only occasionally - say once per several hours - so that shutting down and starting up new VM each time becomes an advantage? Is it possible to create the virtual machine and have it suspended in the background until you need to call to radar interface functions? The VM can be configured through command-line to not consume much of resources so it can live with your main application without conflicts. Wating for your ideas. Pavel. On Wed, Feb 18, 2009 at 6:59 PM, wrote: > Hello, > > I am inquiring about the issue "[drlvm][JNI] Unable to create, destroy, > create VM in the same process." > > mentioned in : > http://issues.apache.org/jira/browse/HARMONY-5505 > > We have a new type of radar with a closed-box Java interface to connect to > a C++ maritime traffic control system. I have made a few JNI prototypes > which seem very promising, but it will run 7/24 and it would be very > advantageous to create, destroy, create VM in the same JNI Invocation > process. > > What is the status of this bug, is the patch to be included in a future > version? > > > > Best regards, > Bert Szoghy > INNAV System > xst.ca >