Andy Yes these should be safely ignorable
The warning means that when the StoreConnection.expel() happened it detected that it was eligible to lock the location and for whatever reason didn't. As for how this happens I am not sure, there are a number of possible race conditions that could occur though in a single process environment most of these are unlikely. In the debugger these all look to be originating from test cases which are calling StoreConnection.release() or StoreConnection.reset() but I don't see why - TS_Store, TS_TransactionTDB and TS_Factory are the culprits from what I see. However running the individual test class that the debugger stops on when I set a breakpoint on the warning does not reliably reproduce the problem. Rob On 25/07/2014 21:21, "Andy Seaborne" <[email protected]> wrote: >Rob, > >I'm getting warnings from the build in jena-tdb: > > >21:11:21 WARN TDB :: Location >/home/afs/Jena/jena-tdb/target/tdb-testing/DB/ was not locked, if >another JVM accessed this location simultaneously data corruption may >have occurred >21:12:18 WARN TDB :: Location >/home/afs/Jena/jena-tdb/target/tdb-testing/DB/ was not locked, if >another JVM accessed this location simultaneously data corruption may >have occurred >21:13:55 WARN TDB :: Location >/home/afs/Jena/jena-tdb/target/tdb-testing/DB/ was not locked, if >another JVM accessed this location simultaneously data corruption may >have occurred > >Are they ignorable (for now) warnings? > > Andy
