Daniel Noll wrote:
This is embedded in an application though so changing the connection properties isn't going to be easy, but do you think changing the system property derby.drda.debug to true on the server would generate enough output to diagnose the problem?
Daniel,I think for a deployed app, derby.client.traceDirectory and derby.client.traceLevel are your best bet for drda tracing. See:
http://wiki.apache.org/db-derby/UndocumentedDerbyBehavior
