I create a large transaction. Keep adding to it. And BANG I kill the client process suddenly.It seems that the transaction keeps hanging on inside derby for some time (maybe a minute or so).
Is this the way it's supposed to be? Derby certainly detects that the connection was broken. Does derby wait for the client to reconnect or something?
For concurrency's and responsiveness' sake it would be better to start the rollback immediately.
- rami
