Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 54445 invoked from network); 16 Jul 2004 13:39:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Jul 2004 13:39:45 -0000 Received: (qmail 51281 invoked by uid 500); 16 Jul 2004 13:39:29 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 51100 invoked by uid 500); 16 Jul 2004 13:39:28 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 50948 invoked by uid 99); 16 Jul 2004 13:39:26 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.27.1) with SMTP; Fri, 16 Jul 2004 06:39:23 -0700 Received: (qmail 7099 invoked from network); 16 Jul 2004 13:40:40 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 16 Jul 2004 13:40:40 -0000 Message-ID: <598072348.1089985240712.JavaMail.apache@nagoya> Date: Fri, 16 Jul 2004 06:40:40 -0700 (PDT) From: dev@geronimo.apache.org To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-264) exceptions being swallowed at startup In-Reply-To: <2101579265.1089662828203.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following issue has been updated: Updater: toby cabot (mailto:toby@caboteria.org) Date: Fri, 16 Jul 2004 6:40 AM Changes: Attachment changed to daemon-log.diff --------------------------------------------------------------------- For a full history of the issue, see: http://issues.apache.org/jira/browse/GERONIMO-264?page=history --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/GERONIMO-264 Here is an overview of the issue: --------------------------------------------------------------------- Key: GERONIMO-264 Summary: exceptions being swallowed at startup Type: Improvement Status: Unassigned Priority: Minor Project: Apache Geronimo Components: deployment Versions: 1.0-M2 Assignee: Reporter: toby cabot Created: Mon, 12 Jul 2004 1:06 PM Updated: Fri, 16 Jul 2004 6:40 AM Environment: fedora core 2 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Description: some exceptions that are thrown during startup are swallowed and don't show up in the logs. i'm at the 'monkey and typewriter' stage of the geronimo learning curve so i'm a good randomness injector. i had a problem where geronimo would try to start up and then go directly to shutdown for no apparent reason. actually, i think i've had a few: 15:50:17,290 DEBUG [GBeanMBean] geronimo.config:name="skeleton/RA" State changed from stopped to starting 15:50:17,292 DEBUG [Configuration] ClassPath for skeleton/RA resolved to [file:/home/tcabot/try/incubator-geronimo/target/config-store/8/connector/skeleton-ra.jar] ra test setting configParameter to NewStringValue 15:50:17,737 DEBUG [SpreadManagedConnectionFactory] BaseManagedConnectionFactory() 15:50:17,737 DEBUG [SpreadManagedConnectionFactory] SpreadManagedConnectionFactory() 15:50:18,425 DEBUG [GBeanMBean] geronimo.config:name="skeleton/RA" State changed from starting to failed 15:50:18,426 INFO [Kernel] Starting kernel shutdown i'll include a patch that logs the problem in the catch clause in Configuration.doStart(). There might be better places to do this, but as long as it gets done *somewhere* i'm happy. regards, toby --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira