ACID Transaction - Empty documents are not rolled back if thread crashes

ACID Transaction creates blank documents on server before commit. If the App crashes before commit - I simulated a app crash by hitting CTRL+C and stopping the java app before it issued commit - all blank docs remain on the server as orphaned docs with empty body. CB needs to roll back these docs if a commit is not done irrespective of what happens to the app thread. App do crash and a crash should not leave the DB is a inconsistent state.