Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 82755 invoked from network); 4 Nov 2001 14:12:40 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 4 Nov 2001 14:12:40 -0000 Received: (qmail 11419 invoked from network); 4 Nov 2001 14:14:58 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 4 Nov 2001 14:14:58 -0000 Received: (qmail 12064 invoked by uid 97); 4 Nov 2001 14:12:39 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 11996 invoked by uid 97); 4 Nov 2001 14:12:38 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 11985 invoked from network); 4 Nov 2001 14:12:38 -0000 From: "Hendrik Schreiber" To: "Avalon Developers List" Subject: AW: AW: AW: AW: Jo! on Phoenix - compile problems Date: Sun, 4 Nov 2001 15:15:29 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <200111032241.fA3Mft228559@mail016.syd.optusnet.com.au> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > The problem is that I can only produce the error when the JVM is force = > shutdown (ie by ctrl-c ing the application) if that is the only situation it occurs, that's good news :-) > So I did a siguit just prior to shutdown. It seems that "get_self" is = the=20 > name of the signal handler for SIGUSR2. It is located in=20 > libhpi.so (an IBM=20 > JVM library). Heres the relevent part of log >=20 > SIGUSR2 : get_self (libhpi.so) Hm. That doesn't tell me anything. Please turn up the log level by setting jo.loglevel in = etc/server.properties to a higher value - maybe 5. Also please set = host.eventloglevel in hosts.properties to 5. There should be some more = info in the log files server.log and event.log (all the things you never = wanted to know :-)). Could you please mail me fresh logfiles with the = loglevels set high. With them I might be able to better point you at = some part in jo! and see where it gets stuck... Thanks, -hendrik -- To unsubscribe, e-mail: For additional commands, e-mail: