On 3/15/2011 6:04 AM, Kathey Marsden wrote:
On 3/15/2011 4:40 AM, Phil Bradley wrote:
Hi Kathey, Knut,
Thanks for your feedback. I had seen bug 4275 but discounted it on the
basis that the problem occurs even after shutting down the database.
Apart from the stack trace, is there something else I can do that will
help to diagnose this? Unfortunately, I can't send you the database as
this would raise data protection issues but if there are any steps that
I can take that will help to diagnose this I'll be happy to submit the
results (I think this is too vague at the moment to raise a bug but if I
can narrow it down, I'll be happy to do this).
Phil one thing I forgot to mention was at the production site I would
definitely upgrade to a release with at least the fix for DERBY-4239.
If you want to stay with 10.4, you can build the latest on the 10.4
branch which has the fix.
