[
https://issues.apache.org/jira/browse/DERBY-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483948
]
Knut Anders Hatlen commented on DERBY-2472:
-------------------------------------------
Does anyone know what this comment in EmbedSQLException means?
/**
Java exception that caused this exception, can be null.
*/
//Because it's transient, it doesn't get sent over to the client
//side and hence the classes which needs to be included in the
//client.jar file decreases 5 folds.
private transient Throwable javaException;
I haven't found any code that serializes (in the meaning
ObjectOutputStream.writeObject()) the exception and sends it over to the
client. If the comment is true, we can't use initCause() on the
EmbedSQLException.
> Use Throwable.initCause() to improve error reporting
> ----------------------------------------------------
>
> Key: DERBY-2472
> URL: https://issues.apache.org/jira/browse/DERBY-2472
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Miscellaneous
> Affects Versions: 10.3.0.0
> Reporter: Kristian Waagan
> Priority: Minor
> Attachments: derby-2472_initial_patch.diff, setStackTrace.diff
>
>
> As Derby has moved to J2SE 1.4, Throwable.initCause() can now be used to
> improve error reporting.
> As stated in the initial commit (that was backed out, see below):
> 'Set Throwable.initCause() in a couple of locations at the JDBC level where
> we setup nested SQLExceptions.
> This means that automatically the stack trace for a database failed to start
> includes the reason
> for the failure, rather than just "see next exception". This is a great help
> when running
> JUnit tests and getting failures to start a database.'
> The initial commit was backed out because it broke numerous tests under JDK
> 1.6, and the author indicated he had no time to investigate.
> The patch caused no failures when running the tests with Java SE 5.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
