File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
OCM Java EE 6 Enterprise Architect Exam Guide
this week in the
Incompatablity between OAS standard edition and enterprise edition
Joined: Jun 28, 2007
Jan 02, 2009 03:00:00
I was previously using OAS enterprise edition now we have migrated to the standard edition.
and now i am facing this problem
: The transaction has been marked for rollback (no reason given)
This happens due to the following code segment
after which a read operation is performed within the same transaction.
We are using
's for transaction management.
So with the same EJB method the transaction is rolled back after which a read operation is performed.
We could argue that this is not the best approach however this is required to achieve the business goals
This same code section happens to be working on the enterprise edition and the standalone server.
Has anyone come across this issue or knows why this happens in case of standard edition or am i missing some thing ??
It is sorta covered in the
JavaRanch Style Guide
subject: Incompatablity between OAS standard edition and enterprise edition
Thread: OAS Setting BMT Transactions as Marked for Rollback - Why?
Locking problems using JDBC and MS SQL Server 2008.
Modification while reading?
How to update an entity when the persistence context is extended?
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014