Primary key violation on JMS_TRANSACTIONS

The calculation of the next transaction id in jms recovery is done in the wrong place.
It should determine the next transaction id before it rolls back incomplete adds
otherwise it will get the next transaction id wrong which could produce
a primary key constraint violation on the JMS_TRANSACTIONS table.