only in direct data access the isolation is valid, thus, only Entities may
have an isolation setted
the isolation level depends on the JTA implementation and varies from DB to
DB, as also the different isolation levels supported
if you´re using Session Beans to access the DB, you're using JDBC code, and
thus, you may set the isolation level desired via JDBC
The 'pessimistic' approach isn't truly so... the main reason this
DeadlockExceptions raise is due to the Entity cache layer in between your
code and the actual DB. May I reccomend you play around with
validity-timeout attrib in orion-ejb-jar.xml? it will reduce DB hits 2
orders of magnitude and surpass all those Deadlock exceptions
HTH
JP
-----Original Message-----
From: David Ekholm [mailto:[EMAIL PROTECTED]]
Sent: Lunes, 11 de Diciembre de 2000 13:10
To: Orion-Interest
Subject: Default transaction isolation level
What is the default transaction isolation level for Orionserver? I would
like to be able to specify this in datasources.xml, but it seems it is only
specifiable in orion-ejb.xml, only pertaining to CMP beans and not session
beans.
The way think it works, Orion default to "Serializable" as CMP beans seem to
obtain exclusive lock when simple getter methods are invoked. A too
pessimistic approach IMHO (In my case this causes DeadlockExceptions)
/David
"The Las Vegas of Online Gaming" David Ekholm
System Architect
Hammarby Kajväg 14, 120 30 Stockholm
tel: +46 (0)8 55 69 67 11
mob: +46 (0)70 486 77 38
fax: +46 (0)8 55 69 67 07
icq: 410993
