Hi Bela,
sorry for not getting back to you sooner on this. We have been busy figuring
out what's going on.
Firstly, the application we ran is on a two node JBoss cluster where each node
has an Updater task and a Reader task which both "update" or "read" the same
1000 entries in the same database table (in oracle).
We set the transaction isolation level to be Serializable.
We configured the TreeCache to be the second level cache of hibernate.
Firstly the problem that we encountered is as follows:
One updater task managed to update the entries inside a transaction, however
the other one periodically failed with an Oracle "cannot serialize transaction
exception".
We think the reason for this is as follows:
Given two transactions A and B as below
transactin A
transaction B
start A |-----------------------------------|
start B |-----------------------------------|
When A commits, B may or may not fail (depending on the common data) due to
state change. In our case transaction B consistently failed as it was working
on the same rows.
So I think we now understand what's happening. Thanks for your help.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885671#3885671
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885671
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
