Sticky KahaDB log files due to local transaction rollback

On a rollback of a local transaction the transaction won't be removed from the inflight transaction list of the KahaDB MessageDatabase. This leads to KahaDB log files which won't be deleted even if there are no messages which are referred by the log file.