No JDBC transactions around storing messages and updating sequence number.

I am curious as to the fact that their is no enclosing transaction around the storing of the messages to the database and the updating of the sequence numbers that happens in Session.sendRaw(). In here, QuickFixJ (if configured for JDBC) updates the database after it has send out the message using:

state.set(msgSeqNum, messageString);
state.incrNextSenderMsgSeqNum();

Both of these update the database, however they don't do it in a single transaction. Doesn't this mean the DB would be in an inconsistent state if the server where to go down between the above two statements.

Indeed I was hoping to be able to hook into this transaction myself to update my own tables so as to ensure that my OMS is always inline with what QuickFix believes it has sent.

I am a relative newbie to QuickFixJ, so please let me know if I am missing the boat entirely.

Many thanks
Paul