I have duplicated the problem I detailed last week on OC4J 1.0.2.2.1. This is a showstopping error, as anytime the server is shut down any bad transactions that deal with updates of beans will be written to the database. This might also affect direct JDBC updates inside a UserTransaction, but I haven't tested it. Does anyone have any insight into why bad data (transactions that say they were rolled back) would be written to the database on shutdown of Orion (or OC4J)?
Jeff.
