there is often more info in derby.log, at least maybe a stack trace for the error. There are a log of "expected" errors in derby.log for this test so looking towards the end usually uncovers the interesting info.

Knut Anders Hatlen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1750?page=comments#action_12430569 ] Knut Anders Hatlen commented on DERBY-1750:
-------------------------------------------

I don't know if it helps (no stack trace), but here's the last part of 
Tester10.log:


Reply via email to