[#DERBY-237] Boot errors from store must not lose error messages/stack traces in between.

Derby

Boot errors from store must not lose error messages/stack traces in between.

Created: 27/Apr/05 02:06 AM Updated: 23/May/05 12:12 PM

Return to search

Component/s:

Store

Affects Version/s:

10.1.1.0

Fix Version/s:

10.1.1.0

Time Tracking:

Not Specified

Environment:

all

Resolution Date:

11/May/05 05:12 AM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Sunitha Kambhampati made changes - 30/Apr/05 08:27 AM

Field	Original Value	New Value
Assignee		Sunitha Kambhampati [ skambha ]

Repository	Revision	Date	User	Message
ASF	#169501	Tue May 10 17:38:06 UTC 2005	mikem	committing fix for ~~DERBY-237~~ for ksunithaghm@gmail.com. This patch fixes ~~DERBY-237~~: Boot errors from store must not lose error messages/stack traces in between. 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
				Files Changed
				MODIFY /incubator/derby/code/trunk/java/engine/org/apache/derby/impl/store/raw/log/LogToFile.java

[ Permlink | « Hide ]

Sunitha Kambhampati added a comment - 11/May/05 05:12 AM

committed with svn 169501.

Sunitha Kambhampati made changes - 11/May/05 05:12 AM

Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]
Fix Version/s		10.1.0.0 [ 10993 ]

Sunitha Kambhampati made changes - 11/May/05 05:25 AM

Status

Resolved [ 5 ]

Closed [ 6 ]

[ Permlink | « Hide ]

Sunitha Kambhampati added a comment - 23/May/05 12:12 PM

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.