-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So, it seems that with derby embedded if a statement in an XA transaction causes a lock timeout two things happen.
1) You can't execute any more statements (reports connection closed) 2) If you try to end the transaction, it fails with XA_RBTIMEOUT Is this the correct behavior for a lock timeout on a single statement? Thanks Kathey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBhqoiG0h36bFmkocRAr02AJ9hc4z9LjooCyte7w8CwjL3d0/xKgCdFVek nIhHo8k30iZJbfji+9qm97E= =VRki -----END PGP SIGNATURE-----
