Hi,
I am here puzzling over the client code; I notived in a test I wrote
that apparently the client driver doesn't "know" that a transaction has
ended on the server when a statement throws an exception of transaction
severity. As far as I could tell, the sending of the state update
happens (only) in DRDAConnThread#writeENDUOWRM, which again is called
only when replying to explicit rollback and commit commands from the
client. Does anyone know if we do anything similar to update the client
state when transaction severity errors are passed back to the client?
The consequence of this that I saw is that a connection "close" failed
on the client without an explicit rollback because it apparently though
the transaction was still active.
Thanks,
Dag
