geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (GERONIMO-264) exceptions being swallowed at startup
Date Fri, 16 Jul 2004 13:48:40 GMT
The following issue has been updated:

    Updater: toby cabot (
       Date: Fri, 16 Jul 2004 6:47 AM
             Attachment changed to daemon-log.diff
For a full history of the issue, see:

View the issue:

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

   Reporter: toby cabot

    Created: Mon, 12 Jul 2004 1:06 PM
    Updated: Fri, 16 Jul 2004 6:47 AM
Environment: fedora core 2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)

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.


This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message