Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 78459 invoked from network); 22 May 2002 13:09:46 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 May 2002 13:09:46 -0000 Received: (qmail 21843 invoked by uid 97); 22 May 2002 13:09:47 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 21806 invoked by uid 97); 22 May 2002 13:09:46 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 21787 invoked by uid 98); 22 May 2002 13:09:45 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <008c01c20192$38d4ac30$8119fea9@klop270> From: "Andrei Ivanov" To: "Avalon-Phoenix Developers List" References: <3CEA39C7.6C9851BE@denic.de> <006e01c2018c$a415da60$8119fea9@klop270> <3CEB939D.8F6A955B@denic.de> <200205222257.12025.peter@apache.org> Subject: Re: Starting phoenix with wrapper problem... Date: Wed, 22 May 2002 16:11:44 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, >eek! First I heard - I changed CLIMain.shutdown() to public and hopefully that >will fix the above. changed to public, builded, and NO MORE exception! Hope you'll update it to cvs. Thanks Andrei ----- Original Message ----- From: "Peter Donald" To: "Avalon-Phoenix Developers List" Sent: Wednesday, May 22, 2002 3:57 PM Subject: Re: Starting phoenix with wrapper problem... On Wed, 22 May 2002 22:48, Ulrich Mayring wrote: > Andrei Ivanov wrote: > > Ok, I made one step forward, problem was that according to wrapper.conf > > which goes with the phoenix, all wrapper files jar, dll, exe and conf has > > to be in dist/bit. It seems so... Now it starts without security > > exception but gives the other one (there is no sar in apps): > > > > jvm 1 | Phoenix 4.0a4 > > jvm 1 | > > jvm 1 | Shutting down Phoenix. > > jvm 1 | java.lang.NoSuchMethodException > > jvm 1 | at java.lang.Class.getMethod0(Native Method) > > jvm 1 | at java.lang.Class.getMethod(Unknown Source) > > jvm 1 | at > > org.apache.avalon.phoenix.launcher.Main.shutdown(Main.java:118) > > This is "normal", i.e. we have it, too, and it doesn't hurt AFAIK. eek! First I heard - I changed CLIMain.shutdown() to public and hopefully that will fix the above. > By > the way, you should always have at least two sars in apps, because if > you only have one, then you can't undeploy (The Management Beans will > die), and if you have no sar at all, then Phoenix used to die (maybe > fixed meanwhile...). Im not sure what you mean. Any time that phoenix has 0 applications deployed it will shutdown (die?) unless you specify "--persistent" on command line. -- Cheers, Peter Donald -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: