Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 76682 invoked from network); 19 Dec 2007 15:13:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Dec 2007 15:13:48 -0000 Received: (qmail 65980 invoked by uid 500); 19 Dec 2007 15:13:35 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 65960 invoked by uid 500); 19 Dec 2007 15:13:35 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 65948 invoked by uid 99); 19 Dec 2007 15:13:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2007 07:13:35 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hemant.malik@gmail.com designates 64.233.162.238 as permitted sender) Received: from [64.233.162.238] (HELO nz-out-0506.google.com) (64.233.162.238) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2007 15:13:14 +0000 Received: by nz-out-0506.google.com with SMTP id x3so1383256nzd.6 for ; Wed, 19 Dec 2007 07:13:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=WlIwv2xY2p8WniNSHOfq+uTMW2rQURcoBJpYSUap0l4=; b=YdViug5Tn+ezUWItjIjmdYaUs6hKmfCOSWKvAuEa6G1KPlRE7QQQubKR6c3X033PvGxoPODYy982CPWKNoKFqHAh4r2AUMa/8ZqUPZ0XJNF19wYZistlq3XDqIaOtETyf2BIIPGOZSOnqwYtrg/KPLUMhnPuGmGxszKUVGQuITg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ZudsUkZTv5WAn+g4mMBZdu7A2MMCBeFHeQnFb3SUAOmladD2oV6BKfFQnTdQ5CWYNo/CSMuSyRvr1ktiLc0AIOTb9yCmOGDT6SuIFkbkiYBM9KRsy5tSm4XVr9THrV5YFaodF+jEXdp39e8clRO0qU1vcsiRc6DCoYTI51YbrLo= Received: by 10.142.187.2 with SMTP id k2mr753264wff.51.1198077197163; Wed, 19 Dec 2007 07:13:17 -0800 (PST) Received: by 10.142.43.9 with HTTP; Wed, 19 Dec 2007 07:13:17 -0800 (PST) Message-ID: <4b6836d40712190713t253d9674m12a20c069c5cca27@mail.gmail.com> Date: Wed, 19 Dec 2007 20:43:17 +0530 From: "Hemant Malik" To: continuum-users@maven.apache.org Subject: Re: JVM Appears to be hung In-Reply-To: <2DD42166EF0A554B83F30B6F7B0CBA5C9DFFFC@derum202.emea.corp.eds.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17318_24821787.1198077197118" References: <4b6836d40711290632v1945e450qb74bb21c7ef2cf78@mail.gmail.com> <474EDA92.8090006@venisse.net> <4b6836d40711290749u2449f603s377933f54785cb85@mail.gmail.com> <4b6836d40711290800p11119997p4d58f8750590aea0@mail.gmail.com> <4b6836d40712022213k4085dd9cm80d72f536f6bfebb@mail.gmail.com> <4b6836d40712022312w5650dd8cpa5e1fbc48b2984df@mail.gmail.com> <2DD42166EF0A554B83F30B6F7B0CBA5C9DFFFC@derum202.emea.corp.eds.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_17318_24821787.1198077197118 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I was able to overcome this problem by deploying continuum war on tomcat. Just browsing through the continuum bug list i came across some bug that wa= s related to jvm and jetty, so just as a wild guess i thought of doing it. An= d on tomcat continuum is running fine. I know there is nothing to infer from this fluke but yeah it worked for me. Regards, Hemant Malik On Dec 19, 2007 7:58 PM, Boeckli, Dominique wrote: > i had same problem and figured out that is was deadlock due to a log4j bu= g > (http://issues.apache.org/bugzilla/show_bug.cgi?id=3D43568): > > This deadlock happens under following cases: > > - Proximity RC9 and Continuum-1.1 on same server > - both has a scheduled task at the same time (a purge task for proximity > and build task for continuum). > > There's no fix for this bug but you can reduce the probability that is > happens: > - don't set start time for proximity and continuum task at the same time. > > brgds > > Dominique > > -----Original Message----- > From: Hemant Malik [mailto:hemant.malik@gmail.com] > Sent: Monday, December 03, 2007 08:13 AM > To: continuum-users@maven.apache.org > Subject: Re: JVM Appears to be hung > > Actually the problem for me is that I don't want the jvm to be killed. > After taking sometime the Apache continuum Console restarts the JVM telli= ng > " JVM appears to be hung...... " which is killing my enqueued processes a= nd > thus losing the schedule :( > > Hemant > > On Dec 3, 2007 12:35 PM, Dan Tran wrote: > > > I had one case where continuum's jvm spined. I had to killl the jvm > > and restart continuum. > > > > my system is jvm 1.5, windows running in non service mode. > > > > > > -D > > > > On Dec 2, 2007 10:13 PM, Hemant Malik wrote: > > > Hi, > > > Has anyone come across a similar problem? I am not able to cope up > > > with > > the > > > "JVM appears to be hung" error. Somebody kindly please help. > > > Is this a bug or am I lacking somewhere? > > > > > > > > > Regards, > > > Hemant Malik > > > > > > > > > On Nov 29, 2007 9:30 PM, Hemant Malik wrote: > > > > > > > I tried increasing the PermSize and Heap Size, but no effect. > > > > > > > > Hemant > > > > > > > > > > > > On Nov 29, 2007 9:19 PM, Hemant Malik > wrote: > > > > > > > > > My OS is Windows XP with SP2. > > > > > > > > > > Regards, > > > > > Hemant Malik > > > > > > > > > > > > > > > On Nov 29, 2007 8:58 PM, Emmanuel Venisse > > wrote: > > > > > > > > > > > What is your OS? > > > > > > > > > > > > Emmanuel > > > > > > > > > > > > Hemant Malik a =E9crit : > > > > > > > Hi, > > > > > > > We are in the phase of adapting to the Continuum as CI tool > > > > > > > here > > at > > > > > > our > > > > > > > organization.We are using the latest version available on > > Continuum > > > > > > Home. > > > > > > > For the testing purposes the Continuum worked beautifully > > > > > > > but > > with > > > > > > actual > > > > > > > project from CVS, its taking quite a bit of time, after the > > checkout > > > > > > when I > > > > > > > give the build command, after waiting for certain time "JVM > > appears > > > > > > to be > > > > > > > hung" error comes and the JVM gets restarted, hence I loose > > > > > > > the > > > > > > earlier > > > > > > > progress in the build. > > > > > > > > > > > > > > Could please someone help out as if it is a configuration > > problem > > > > > > somewhere > > > > > > > or anything more serious? > > > > > > > The exact error is : > > > > > > > "* > > > > > > > ERROR | wrapper | 2007/11/29 19:17:18 | JVM appears hung: > > Timed > > > > > > out > > > > > > > waiting for signal from JVM. > > > > > > > ERROR | wrapper | 2007/11/29 19:17:18 | JVM did not exit > > > > > > > on > > > > > > request, > > > > > > > terminated > > > > > > > STATUS | wrapper | 2007/11/29 19:17:24 | Launching a > > > > > > > JVM...* " > > > > > > > > > > > > > > Regards, > > > > > > > Hemant Malik > > > > > > > > > > > > > > We are working with : > > > > > > > 1) Maven 2.0.7 > > > > > > > 2) CVS > > > > > > > 3) Continuum 1.1 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------=_Part_17318_24821787.1198077197118--