Re: db4o11-7.4 AbstractMethodError

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/14/2012 10:52 PM, Dennis Nezic wrote:
> On Tue, 14 Aug 2012 11:40:49 -0400, Steve Dougherty wrote:
>> On 08/14/2012 08:56 AM, Dennis Nezic wrote:
>>> On Fri, 10 Aug 2012 15:47:35 -0400, Steve Dougherty wrote:
>>>> Any idea what may have changed before this problem started 
>>>> happening? What version of ant are you using to build?
>>> 
>>> That's what I'm pulling my hair trying to find out! I only
>>> upgraded a few system packages on my machine, like glib,
>>> libffi, ... -- and nothing much else! But how can a seemingly
>>> unrelated system package have such a huge effect in a Java
>>> environment??
>>> 
>>> I haven't changed my jdk (although recently I did test with 
>>> others, sun-jdk and icedtea-bin), I haven't changed my ant, I 
>>> haven't changed my db4o's, I recompiled all of Freenet's
>>> (direct) dependencies. This is incredibly frustrating. I mean,
>>> 1407 WAS working before, and now it's not :S.
>>> 
>>> Here are the types of AbstractMethodError's that arise:
>>> 
>>> 
>>> java.lang.AbstractMethodError: 
>>> com.db4o.internal.query.ObjectSetFacade.iterator 
>>> ()Ljava/util/Iterator;
>>> 
>>> 
>> at freenet.client.async.ClientRequestScheduler.loadKeyListeners
>>> (ClientRequestScheduler.java:114) [code]
>>> ObjectSet<HasKeyListener> results = Db4oBugs.query (container,
>>> HasKeyListener.class); for (HasKeyListener l : results) {
>>> <--- ** 114 [/code]
>>> 
>>> 
>>> java.lang.AbstractMethodError: 
>>> com.db4o.internal.query.ObjectSetFacade.iterator 
>>> ()Ljava/util/Iterator;
>>> 
>>> 
>> at
>> freenet.client.async.PersistentStatsPutter.restorePreviousData
>>> (PersistentStatsPutter.java:44) [code] 
>>> ObjectSet<BandwidthStatsContainer> BSCresult = container.query 
>>> (BandwidthStatsContainer.class); for (BandwidthStatsContainer 
>>> candidate : BSCresult) {   <--- ** 44 [/code]
>> 
>> So what did you do to establish that your database is not
>> corrupted? These are internal db4o errors.
> 
> Hmm. So it does seem as though my datastore was corrupted. Deleting
> it, and making my node create a new one got me up and running
> again. Thanks Steve!
> 
> The odd thing is a bunch of us[1] have been getting this error / 
> corruption since about the time build1409 came out. I sure hope
> it's just a freak coincidence :S.
> 
> [1] https://bugs.gentoo.org/show_bug.cgi?id=429716
> 

Your _datastore_ was corrupted, not your node.db4o(.crypt)?! What
exactly did you do to get your node running again?

Do you think you could try git-bisect to determine which commit
introduced this problem, or are you not able to reproduce it at will?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJQKxxrAAoJECLJP19KqmFufHYQAKQxgR3hM64C4TluZIc9g02A
zIH/EDlQT2aoJpCPueTY7COgvFg59VRFReumclrJS2tUiUx8rXjv8m3egz/s/YrR
RBNnwAx9Z09tZucAGwUE84pnXDulWTuTSUvmouOTwtqUSyP6jDcR6OwHC0akcbn1
wqBT+7cQzXTSOhzfP12eTWDM9MaAj7qL5Lt+lRBApdCVzUA1rxQfN/nEmqnIBFp9
gB4JI2Xg+Howw4zv7OoxsiJwmDU6QzK/Q0GHklY7PmKad/oo9+koKVlADoAj8aqP
5oceKTmb4zLYVZdERvm+Vz9G7zDB/hy00jwPN0eyt4+LN+CkKL3ksbKVs+5Dg4IA
0/DQJ17AsKxQWIsWsHcaoYtvg6cYXOACrYGSKa31jQJ7UIKfhmlitnwYlrfG9Bzr
BVaofIszv9xg5pzBZcXJXl0m60cpPP8dUJGQCjXlHEq1mKfji8lklVDz0LacNUBT
QGw2HHl0mVh0ktV7pSbQhwl7SKDfBTxlEZYDVpXTiCrre6HXjgcemI0luM+uaZhy
9qxh5CM+k4F1dUOrXFwSewrZe6BfVTVEEvE8UlYOGwP8sTb08DCPdx1iKOZCC54Q
WiLTNsHWk7MmAZRug/830E+CTl9AFdc/Lyydsum6CmnKRfGLEmFMsYJUHG8Kl9Gw
kneCZIF2X7pNpOhURkWn
=SbPZ
-----END PGP SIGNATURE-----
_______________________________________________
Support mailing list
[email protected]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-request-RdDMkVZAZeuJnvDnx1genB2eb7JE58TQ@public.gmane.org?subject=unsubscribe