[bisq-network/bisq] Bisq stalls for 10 seconds while starting during Bitcoin node detection if firewall enabled (#4073)

[dmos62]

The 10 second delay is quite weird. If it's just the `socket.connect()` timing out, it should be 5 seconds. Would be interesting to know what is happening during those 10 seconds.

Things I'd like to check:
- Insert a `log.info("About to check for a Local Bitcoin node on port {}", port);` right at the beginning of `LocalBitcoinNode::detect(int port)`, so that we know when exactly the socket check begins.
- Is it always 10 seconds? A few samples would be insightful.
- Does `--ignoreLocalBtcNode=true` eliminate the delay?
- If you replace `this.useTorForBTC.set(preferences.getUseTorForBitcoinJ());` (WalletAppSetup:93) with `this.useTorForBTC.set(false);`, that will move the checking outside Guice init; does that change its delay?

Unfortunately, I can't reproduce this either. @wiz could you help debug?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4073#issuecomment-600572248
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200318/8825859f/attachment.html>