<p>Maybe we miss the BSQ wallet keys in the bloomfilter. As all BSQ tx have BTC we still hear from the network but maybe not that call back at sending?</p>
<p>I just tried with changing the way who we clone and on which wallet we do the broadcast but that did not had any influence, got the timeout again.  Referred to WalletManager.publishAndCommitBsqTx...</p>
<p>What is weird is that we get from one peer a lot of messages after the broadcast. I saw this 2 times now with a diff. peer. I think the first one was with getAddr calls. At another try I did not get those msg again... so prob. not related but still weird....</p>
<p>Apr-04 09:52:25.666 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@4c96160b<br>
Apr-04 09:52:25.666 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 1 items gathered from listeners to peer<br>
Apr-04 09:52:26.056 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@e496f6a<br>
Apr-04 09:52:26.056 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 2 items gathered from listeners to peer<br>
Apr-04 09:52:26.253 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@400f2cb6<br>
Apr-04 09:52:26.253 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 2 items gathered from listeners to peer<br>
Apr-04 09:52:26.449 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@f29df925<br>
Apr-04 09:52:26.449 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 1 items gathered from listeners to peer<br>
Apr-04 09:52:26.638 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@a338db17</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/2639#issuecomment-479932553">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZthTG653xhA05JiPMMJux-I3_rFm-ks5vdhLZgaJpZM4cc6uc">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtiqfZSIiYOazYEMMe2bfEFxTaAk1ks5vdhLZgaJpZM4cc6uc.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq","title":"bisq-network/bisq","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ManfredKarrer in #2639: Maybe we miss the BSQ wallet keys in the bloomfilter. As all BSQ tx have BTC we still hear from the network but maybe not that call back at sending? \r\n\r\nI just tried with changing the way who we clone and on which wallet we do the broadcast but that did not had any influence, got the timeout again.  Referred to WalletManager.publishAndCommitBsqTx...\r\n\r\nWhat is weird is that we get from one peer a lot of messages after the broadcast. I saw this 2 times now with a diff. peer. I think the first one was with getAddr calls. At another try I did not get those msg again... so prob. not related but still weird....\r\n\r\nApr-04 09:52:25.666 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@4c96160b \r\nApr-04 09:52:25.666 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 1 items gathered from listeners to peer \r\nApr-04 09:52:26.056 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@e496f6a \r\nApr-04 09:52:26.056 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 2 items gathered from listeners to peer \r\nApr-04 09:52:26.253 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@400f2cb6 \r\nApr-04 09:52:26.253 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 2 items gathered from listeners to peer \r\nApr-04 09:52:26.449 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@f29df925 \r\nApr-04 09:52:26.449 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Sending 1 items gathered from listeners to peer \r\nApr-04 09:52:26.638 [NioClientManager] INFO  org.bitcoinj.core.Peer: [46.101.199.114]:18333: Received getdata message: org.bitcoinj.core.GetDataMessage@a338db17 \r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2639#issuecomment-479932553"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2639#issuecomment-479932553",
"url": "https://github.com/bisq-network/bisq/issues/2639#issuecomment-479932553",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>