[Mulgara-dev] Backups failing Mulgara 1.2 Windows

[Ben Hysell]

Alex,

I sent out the result files from the testing yesterday.  The size of the
two files exceeded the list serve max and they needed list admin
approval before they went out to everyone. 

The short version is there were a lot of null pointer exceptions like:

AdvDatabaseSessionUnitTest	testDatabaseDelete	Error	N/A

java.lang.NullPointerException
at org.mulgara.util.MappedIntFile.unmap(MappedIntFile.java:313)
at org.mulgara.util.IntFile.close(IntFile.java:376)
at org.mulgara.util.IntFile.delete(IntFile.java:345)
at org.mulgara.store.xa.FreeList.delete(FreeList.java:398)
at
org.mulgara.store.xa.ManagedBlockFile.close(ManagedBlockFile.java:217)
at
org.mulgara.store.xa.ManagedBlockFile.delete(ManagedBlockFile.java:180)
at
org.mulgara.store.statement.xa.TripleAVLFile.delete(TripleAVLFile.java:3
33)
at
org.mulgara.store.statement.xa.XAStatementStoreImpl.delete(XAStatementSt
oreImpl.java:664)
at
org.mulgara.resolver.store.StatementStoreResolverFactory.delete(Statemen
tStoreResolverFactory.java:140)
at org.mulgara.resolver.Database.delete(Database.java:863)
at
org.mulgara.resolver.AdvDatabaseSessionUnitTest.testDatabaseDelete(AdvDa
tabaseSessionUnitTest.java:1552)

  

-----Original Message-----
From: mulgara-dev-bounces at mulgara.org
[mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of Alex Hall
Sent: Wednesday, April 09, 2008 3:11 PM
To: Mulgara Developers
Subject: Re: [Mulgara-dev] Backups failing Mulgara 1.2 Windows

Ben Hysell wrote:
> Alex,
> 
> Applied the patch...the restore succeeds, the backup fails.
> 
> Applied the same patch to MappedBlockFile, backups succeeds.
> 
> Alex, have you tried doing a 'build test' with the patched code?  Are
you getting any odd results?

No, I haven't tried that yet.  I'm working on other projects at the 
moment and don't have the time to run the full tests (it takes too long 
on my laptop).

> Before the patch 98% pass, after 82.98, 80, 83.31 (I'm getting
different Success rates on subsequent runs) 
> 
> Thoughts?

Sure...  My thoughts are, we're doing weird stuff with the garbage 
collector and filesystem that developers like us probably weren't meant 
to do.  Paul and Andrae can probably list a whole host of reasons why 
applying that patch is a bad idea.  I only suggested that it might fix 
the backup/restore problem, not that it wouldn't break other things ;-)

All kidding aside, the fact that the success rates vary for different 
runs suggests that it's a timing issue.  This isn't very surprising 
given that we're mucking around with the internal workings of the 
garbage collector.  When the tests don't pass, is it due to failed 
assertions or to exceptions being thrown?  Are there any stack traces 
you can share?

Alex

_______________________________________________
Mulgara-dev mailing list
Mulgara-dev at mulgara.org
http://mulgara.org/mailman/listinfo/mulgara-dev