From: Mircea Markus <mircea.markus@jboss.com>

Subject: Re: Weird filesystem issues breaking transaction tests in CI

Date: November 9, 2011 2:34:24 PM GMT+01:00

To: Galder Zamarreņo <galder@jboss.org>

Cc: Dan Berindei <dberinde@redhat.com>

The volatile store form JBossTM is now disabled - I had played with recovery and I forgot it on. 

This should be fixed once https://github.com/infinispan/infinispan/pull/629 is integrated.

On 9 Nov 2011, at 13:04, Galder Zamarreņo wrote:

Hey guys,

So, I've been analysing the failures in:

https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.infinispan$infinispan-core/305/testReport/junit/org.infinispan.tx/TransactionsSpanningDistributedCachesTest/org_infinispan_tx_TransactionsSpanningDistributedCachesTest_testCommitSpanningCaches/

and

https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/303/consoleText

And I think there's a common denominator:

In the 1st test, just before the failure, you see:
java.io.FileNotFoundException: PutObjectStoreDirHere/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0ad62fc1_ab2a_4eba5393_172 (No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.write_state(ShadowingStore.java:557)
at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.write_committed(FileSystemStore.java:134)
at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2209)
at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1469)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:99)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:159)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1158)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:119)
at org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testCommitSpanningCaches(TransactionsSpanningReplicatedCachesTest.java:103)

And in the 2nd, you see:
Caused by: com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ARJUNA12225: FileSystemStore::setupStore - cannot access root of object store: PutObjectStoreDirHere/ShadowNoFileLockStore/defaultStore/
at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.<init>(FileSystemStore.java:482)
at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.<init>(ShadowingStore.java:619)
at com.arjuna.ats.internal.arjuna.objectstore.ShadowNoFileLockStore.<init>(ShadowNoFileLockStore.java:53)

Maybe it's some issue with Cloudbees and the filesystem, so I'm wondering, can we have an alternative transaction store? i.e. one in memory to avoid these kid of issues?

Could you look at alternatives in JBoss TS for this?

In the mean time, I'll check with Cloudbees to see what's up.

Cheers,
--
Galder Zamarreņo
Sr. Software Engineer
Infinispan, JBoss Cache