search

novitski / bitcoinj

Automatically exported from code.google.com/p/bitcoinj
Apache License 2.0
0 stars 0 forks source link

NullPointerException: Clearing filters is not currently supported #583

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I see this exception from time to time in the logs. This is with bitcoinj 0.12.

java.lang.NullPointerException: Clearing filters is not currently supported
        at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229) ~[na:0.0]
        at org.bitcoinj.core.Peer.setBloomFilter(Peer.java:1574) ~[na:0.0]
        at org.bitcoinj.core.PeerGroup.recalculateFastCatchupAndFilter(PeerGroup.java:938) ~[na:0.0]
        at org.bitcoinj.core.PeerGroup$1.onBlocksDownloaded$78aea4c1(PeerGroup.java:149) ~[na:0.0]
        at org.bitcoinj.core.Peer$8.run(Peer.java:1024) ~[na:0.0]
        at org.bitcoinj.utils.Threading$2.execute(Threading.java:140) ~[na:0.0]
        at org.bitcoinj.core.Peer.invokeOnBlocksDownloaded(Peer.java:1021) ~[na:0.0]
        at org.bitcoinj.core.Peer.endFilteredBlock(Peer.java:957) ~[na:0.0]
        at org.bitcoinj.core.Peer.processMessage(Peer.java:335) ~[na:0.0]
        at org.bitcoinj.core.PeerSocketHandler.receiveBytes(PeerSocketHandler.java:178) ~[na:0.0]
        at org.bitcoinj.net.ConnectionHandler.handleKey(ConnectionHandler.java:217) ~[na:0.0]
        at org.bitcoinj.net.NioClientManager.run(NioClientManager.java:111) ~[na:0.0]
        at com.google.common.util.concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:60) ~[na:0.0]
        at com.google.common.util.concurrent.Callables$3.run(Callables.java:93) ~[na:0.0]
        at java.lang.Thread.run(Thread.java:841) ~[na:0.0]

Original issue reported on code.google.com by andreas....@gmail.com on 19 Oct 2014 at 8:02

Attachments:

GoogleCodeExporter commented 9 years ago 
What's up with ~[na:0.0] ?

Original comment by mh.in.en...@gmail.com on 20 Oct 2014 at 11:53

GoogleCodeExporter commented 9 years ago 
I think you can ignore that. I'm not sure what it means, but it happens when 
you log exceptions in a different thread than the UI thread.

Original comment by andreas....@gmail.com on 20 Oct 2014 at 12:02