Message: The following issue has been re-assigned.
Assignee: Dain Sundstrom (mailto:[EMAIL PROTECTED]) Assigner: Jeremy Boynes (mailto:[EMAIL PROTECTED]) Date: Fri, 16 Jul 2004 10:39 AM Comment: Toby, thanks The reason this class was using System.err was because it was running before the logging subsystem had chance to start. I'm going to assign this to Dain as he is more familiar with logging and would know if this is a valid thing to do. --------------------------------------------------------------------- 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: Open Priority: Minor Project: Apache Geronimo Components: deployment Versions: 1.0-M2 Assignee: Dain Sundstrom Reporter: toby cabot Created: Mon, 12 Jul 2004 1:06 PM Updated: Fri, 16 Jul 2004 10:39 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
