Hmmmm I believe I ran into similar issues a while back - have you tried whitelisting the IP of your bitcoinj client in the Bitcoin Core conf?
I also vaguely recall getting stalled connections from time to time and adding logic in my app to hack around it by disconnecting and reconnecting. On Sun, Dec 2, 2018 at 4:51 PM Manfred Karrer <[email protected]> wrote: > Here is a bug report form a user as well: > https://github.com/bisq-network/bisq/issues/1823 > > Here is the fork we are using: > https://github.com/bisq-network/bitcoinj/commits/bisq_0.14.4.1 > > > Am Sonntag, 2. Dezember 2018 18:53:49 UTC+1 schrieb Manfred Karrer: >> >> When having latest Bitcoin Core running in testnet and starting a new >> BitcoinJ instance (Bisq, using latest BitcoinJ release) I get download >> stalled at 91MB (as seen in Bictoin Core debug window) then gets >> disconnected from Bitcoin Core and then reconnects but gets very low >> bandwidth. Seems Bitcoin Core added some ddos protection. I never observed >> that in earlier versions. Does anyone know how to avoid that issue? >> >> With mainet it seems even lower, about 7,8 MB. >> >> I can reproduce that with each fresh start (deleting Bisq app directory >> so it starts as new node again). >> >> Br, >> Manfred >> > -- > You received this message because you are subscribed to the Google Groups > "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
