On Wednesday, February 24, 2016 05:38:09 PM Matthew Toseland wrote: > >> The message should have been matched anyway: Unmatched messages (in > >> MessageCore are added to a data structure and we check before timing out > >> the waitFor()). Possibly a concurrency issue, I thought I'd debugged all > >> such problems ages ago. :( > It seems unlikely that a race condition like that would happen reliably, > so I don't know what is happening here.
I looked at the log output again and found that the problem might be that an unmatched message from a source that is not routable gets still marked as matched. In my case, it's the FNPBulkPacketSend-message that gets fed to the NodeDispatcher before the actual noderef-receiver thread starts. And since it gets marked as matched, it won't be passed to the receiver thread later on. This behavior was introduced near the end of last year [1]. However, I'm not sure if the problem lies in the fact that the message gets marked as matched although it actually doesn't seem to be or if the source (in my case, it is a SeedServerPeerNode) should normally be considered as routable. What do you think? In my case, reverting the commit mentioned above solved the problem. Martin [1] https://github.com/freenet/fred/commit/f3e3be45698272db462ae45f784ff4049c692e92 _______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
