Are you using EJB 3 (CMT/BMT) or Seam-managed tx's?
The latter, seam-managed transactions.
Facing similar problem. http://www.seamframework.org/Community/WhyOrghibernateLazyInitializationExceptionOnRollback
Please assist. Thank you in advance.
Note: I guess using SMPC and related transactions annotated with @Transactional.
Quoting from the JPA spec, 3.3.2 Transaction Rollback
For both transaction-scoped and extended persistence contexts, transaction rollback causes all pre-existing managed instances and removed instances to become detached. The instances’ state will be the state of the instances at the point at which the transaction was rolled back. Transaction rollback typically causes the persistence context to be in an inconsistent state at the point of rollback. In particular, the state of version attributes and generated state (e.g., generated primary keys) may be inconsistent. Instances that were formerly managed by the persistence context (including new instances that were made persistent in that transaction) may therefore not be reusable in the same manner as other detached objects—for example, they may fail when passed to the merge operation.
If you get a rollback, it very much depends why it happened. Unless you try to discover the root cause, it's better to discard all data.