JBosscache dirty read even though isolation is REPEATABLE_RE

[vishwasoft]

I'm trying to evaluate the JBossCache for our application
I'm getting dirty read even though I rollback transaction. I tried this with EJB3 Stateless session bean BMT.

Could you please anyone help me on this prolbem, Am I making anything wrong?

Here is the code

public class TestEntity {

private int array[] = new int[100000];

public void update(int value) {

for (int i = 0; i < array.length; i++) {
array [ i ]=value;
}

}

public int[] getArray() {
return array;
}
}


Stateless Bean code to update cache

Stateless Bean 1

public void updateArray(int value) {
TransactionManager tm = cache.getConfiguration().getRuntimeConfig().getTransactionManager();
try {
tm.begin();
String key = node.getFqn().toString();
TestEntity t = (TestEntity) node.get(key);
if(t != null) {
t.update(value);
node.put(key, t);
}
tm.rollback();
} catch (Exception e) {
try {
tm.rollback();
}catch(Exception ex1) {
ex1.printStackTrace();
}
e.printStackTrace();
}
}

Stateless Bean 2 to read and validating array

public boolean validateArray() {
TransactionManager tm = cache.getConfiguration().getRuntimeConfig().getTransactionManager();
try {
tm.begin();
cache.getInvocationContext().getOptionOverrides().setForceWriteLock(true);
int a[] = readArray();
int value = a[0];
for (int i = 0; i < a.length; i++) {
if(a != value) {
System.out.println(a+":"+value);
sctx.getUserTransaction().rollback();
return false;
}
}
tm.commit();
}catch(Exception ex) {
try {
tm.rollback();
}catch(Exception ex1) {
ex1.printStackTrace();
}
ex.printStackTrace();
}
return true;
}

Configuration file:
I have used configuration file example for cache configuration

[vishwasoft]

I have tried with Isolation level READ_COMMITTED also.

I have replaced array in my TestEntity object, but still the same problem

[mircea.markus]

Are you running both EJB's in the same JVM? That would explain it, as TX rollback won't affect the changes you've done to TestEntity, only the operations you've done on cache. That is the changes TestEntity.update does on the object won't be affected by the TransactionManager.rollback call. Following will be affected though:

cache.put(fqn, "key", "1");
tm.begin();
cache.put(fqn, "key", "2");
tm.rollback();
assert cache.get(fqn, "key").equals("1") : "this is true, won't fail!!!";

[mircea.markus]

On the other post I saw you're using DummyTransactionManagerLookup. You're running in the application server so use GenericTransactionManagerLookup.

[vishwasoft]

Thank you for timely reply.

Yes, I'm running cache & EJB in same JVM.

This is the case, I need to look for alternative design.

Thank you very much