for DERBY-491, I was expecting to see a protocol exception for the first test case (DERBY-491), not a hang.

Interesting. That's my expectation too, so I'm not sure I understand
why the behavior changed.

Good catch! Let me investigate this and see if I can learn more about
what this new behavior is.

thanks,

bryan


Reply via email to