UDPPacket.verifyNotReleased() logic inverted

[zab]

The following logic is inverted:

private void verifyNotReleased() {
        if (CACHE) return; // < but it should be if (!CACHE)

I'm marking it as major priority since it could be masking concurrency issues of unknown severity.

[zab]

After applying this patch on vanilla trunk ​http://pastethis.i2p/show/1464/ KillYourTV reported the following report ​http://pastethis.i2p/show/1467/ which confirms that this inverted logic is in fact masking concurrency bugs in the production build (as opposed to an artifact produced by any of my experimental changes):

after 28 minutes:

7/21/12 10:02:52 AM CRIT [DPReceiver.1] router.transport.udp.UDPPacket: my trace
     java.lang.Exception
     at net.i2p.router.transport.udp.UDPPacket.logReleaseReport(UDPPacket.java:337)
     at net.i2p.router.transport.udp.UDPPacket.verifyNotReleased(UDPPacket.java:323)
     at net.i2p.router.transport.udp.UDPPacket.getLifetime(UDPPacket.java:138)
     at net.i2p.router.transport.udp.UDPReceiver.doReceive(UDPReceiver.java:163)
     at net.i2p.router.transport.udp.UDPReceiver.receive(UDPReceiver.java:136)
     at net.i2p.router.transport.udp.UDPReceiver.access$700(UDPReceiver.java:22)
     at net.i2p.router.transport.udp.UDPReceiver$Runner.run(UDPReceiver.java:259)
     at java.lang.Thread.run(Thread.java:722)
     at net.i2p.util.I2PThread.run(I2PThread.java:85)
7/21/12 10:02:52 AM CRIT [DPReceiver.1] router.transport.udp.UDPPacket: previous releaser id 65 name UDP Packet handler 2/5
7/21/12 10:02:52 AM CRIT [DPReceiver.1] router.transport.udp.UDPPacket: double release!

[zzz]

Good catch, bug from 2005.

Since it's only logging, won't fix it until after the 0.9.1 release so people don't generate more bug reports.

[zzz]

Fixed in 0.9.1-2 with level changed to ERROR.