Forums Register Login

Isolation issue with Oracle in EJB

+Pie Number of slices to send: Send
We are experiencing problems (ORA-08177 can not serialize exception during long transaction) during concurrent access from multiple transaction. We have all our Session and Entity Beans with
TX_ATTRIBUTE : TX_REQUIRED
ISOLATION LEVEL : TX_SERIALIZABLE
Persistance : BMP
Transaction : CMT
Is there KNOWN problem with Oracle databse-- basically the problem being that Oracle's isolation levels don't map well to the EJB specification.
I tried IBM web site for tech Support, this kind of bug not reported any where.
Could some one give some insight?
Thanks
Alagan
To get a wish, you need a genie. To get a genie, you need a lamp. To get a lamp, you need a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 971 times.
Similar Threads
Specifying Transaction Duration
EJB's support for: Nested Transaction / 2 Phase Commit / Isolation Level
do we need to change transaction isolation level during life of a connection?
question on concurrency control, transaction, BMT
Data Caching in EJB application
More...

All times above are in ranch (not your local) time.
The current ranch time is
Apr 16, 2024 06:28:47.