geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-264) exceptions being swallowed at startup
Date Sat, 09 Jul 2005 23:22:10 GMT
     [ ]
Aaron Mulder resolved GERONIMO-264:

    Fix Version: 1.0-M4
     Resolution: Fixed
      Assign To: Aaron Mulder  (was: Dain Sundstrom)

Tony noted that the new startup sequence obsoletes this patch

> exceptions being swallowed at startup
> -------------------------------------
>          Key: GERONIMO-264
>          URL:
>      Project: Geronimo
>         Type: Improvement
>   Components: deployment
>     Versions: 1.0-M2
>  Environment: fedora core 2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
>     Reporter: toby cabot
>     Assignee: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0-M4
>  Attachments: Daemon-1_9-diff.txt, Daemon-56609-diff.txt, Daemon-r159681-diff.txt, daemon-log.diff,
daemon-log.diff, log.txt
> some exceptions that are thrown during startup are swallowed and don't show up in the
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message