db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-237) Boot errors from store must not lose error messages/stack traces in between.
Date Mon, 23 May 2005 03:22:54 GMT
     [ http://issues.apache.org/jira/browse/DERBY-237?page=comments#action_66022 ]
     
Sunitha Kambhampati commented on DERBY-237:
-------------------------------------------

Changes that went in as part of svn 169501.

Actually nested exceptions from the boot error were not lost but their stack traces were not
being written out into error stream which is why the entire stack traces of exceptions was
not printed out to derby.log

-- tested it with a corrupted database (from derby 241) that resulted in boot error and the
stack traces are printed out ok in derby.log.


> Boot errors from store must not lose error messages/stack traces in between.
> ----------------------------------------------------------------------------
>
>          Key: DERBY-237
>          URL: http://issues.apache.org/jira/browse/DERBY-237
>      Project: Derby
>         Type: Bug
>   Components: Store
>     Versions: 10.1.0.0
>  Environment: all
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>      Fix For: 10.1.0.0

>
> Boot errors from store do not show the entire stack traces of the nested exceptions
> We need to print the entire stack trace without losing exceptions in between. This will
save time to debug errors. 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message