<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=26766114" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/dunkfan">@dunkfan</a> Did this happen to you once when you tried to take this specific offer or every time and for any offer you tried to take?</p>
<pre><code>Apr.-26 00:26:04.625 [JavaFX Application Thread] ERROR b.c.o.a.OfferAvailabilityProtocol: AckMessage for OfferAvailabilityResponse failed. AckMessage=AckMessage{
uid='672afa79-3bc8-4d81-9951-ea003cd8d5b8',
senderNodeAddress=klgpg3m7xu36yqkd.onion:9999,
sourceType=OFFER_MESSAGE,
sourceMsgClassName='OfferAvailabilityResponse',
sourceUid='c39f4490-f2ec-462f-9277-9e9b8e3dfde8',
sourceId='86436211-4d14de04-ed77-4d58-bb44-6f5270cfb1ad-101',
success=true,
errorMessage='null'
} NetworkEnvelope{
messageVersion=10
}, makersNodeAddress=rczscnooqxftn2zo.onion:9999, errorMessage=We did not send the EncryptedMessage because the peer does not support the capability.
Apr.-26 00:26:13.526 [AbstractTimeoutHandler timeouts] INFO o.b.c.PeerSocketHandler: [r3dsojfhwcm7x7p6.onion]:8333: Timed out
Apr.-26 00:26:13.526 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] ERROR o.b.n.BlockingClient: Error trying to open/read from connection: r3dsojfhwcm7x7p6.onion:8333: Connect timed out
Apr.-26 00:26:13.533 [AbstractTimeoutHandler timeouts] INFO o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died (8 connected, 0 pending, 9 max)
Apr.-26 00:26:13.540 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] INFO o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died (8 connected, 0 pending, 9 max)
</code></pre>
<p>It looks like there was a connection problem with your trading peer. Was the offer still available in the offer book after the error? It might be the case that the peer just stopped the client.</p>
<p>I also saw following warnings regarding the deposit transaction. Not sure if this is something that can be ignored in that case.</p>
<pre><code>Apr.-26 00:27:23.655 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
Apr.-26 00:27:23.671 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null
</code></pre>
<p>Either the deposit transaction wasn't created or the <code>depositTxId</code> or <code>takeOfferDate</code> was null. As the takeOfferDate is initialized in the constructor it is probably the depositTxId that was null in that case.</p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1449498" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ManfredKarrer">@ManfredKarrer</a> Is it the case if the deposit transaction is never sent out that it will be reseted on time out and creates this kind of warning. Just to be sure we are not overlooking some issue.</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/2785#issuecomment-486985403">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRHAEVI6GUI56HLLLTPSLA2BANCNFSM4HIRFBSA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNX3IA4VERSUY5DPEW3PSLA2BANCNFSM4HIRFBSA.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":"@ripcurlx in #2785: @dunkfan Did this happen to you once when you tried to take this specific offer or every time and for any offer you tried to take?\r\n```\r\nApr.-26 00:26:04.625 [JavaFX Application Thread] ERROR b.c.o.a.OfferAvailabilityProtocol: AckMessage for OfferAvailabilityResponse failed. AckMessage=AckMessage{\r\n uid='672afa79-3bc8-4d81-9951-ea003cd8d5b8',\r\n senderNodeAddress=klgpg3m7xu36yqkd.onion:9999,\r\n sourceType=OFFER_MESSAGE,\r\n sourceMsgClassName='OfferAvailabilityResponse',\r\n sourceUid='c39f4490-f2ec-462f-9277-9e9b8e3dfde8',\r\n sourceId='86436211-4d14de04-ed77-4d58-bb44-6f5270cfb1ad-101',\r\n success=true,\r\n errorMessage='null'\r\n} NetworkEnvelope{\r\n messageVersion=10\r\n}, makersNodeAddress=rczscnooqxftn2zo.onion:9999, errorMessage=We did not send the EncryptedMessage because the peer does not support the capability. \r\nApr.-26 00:26:13.526 [AbstractTimeoutHandler timeouts] INFO o.b.c.PeerSocketHandler: [r3dsojfhwcm7x7p6.onion]:8333: Timed out \r\nApr.-26 00:26:13.526 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] ERROR o.b.n.BlockingClient: Error trying to open/read from connection: r3dsojfhwcm7x7p6.onion:8333: Connect timed out \r\nApr.-26 00:26:13.533 [AbstractTimeoutHandler timeouts] INFO o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died (8 connected, 0 pending, 9 max) \r\nApr.-26 00:26:13.540 [BlockingClient network thread for r3dsojfhwcm7x7p6.onion:8333] INFO o.b.c.PeerGroup: [r3dsojfhwcm7x7p6.onion]:8333: Peer died (8 connected, 0 pending, 9 max)\r\n```\r\nIt looks like there was a connection problem with your trading peer. Was the offer still available in the offer book after the error? It might be the case that the peer just stopped the client.\r\n\r\nI also saw following warnings regarding the deposit transaction. Not sure if this is something that can be ignored in that case. \r\n```\r\nApr.-26 00:27:23.655 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null \r\nApr.-26 00:27:23.671 [JavaFX Application Thread] WARN b.c.trade.Trade: depositTx is null\r\n```\r\nEither the deposit transaction wasn't created or the `depositTxId` or `takeOfferDate` was null. As the takeOfferDate is initialized in the constructor it is probably the depositTxId that was null in that case. \r\n\r\n@ManfredKarrer Is it the case if the deposit transaction is never sent out that it will be reseted on time out and creates this kind of warning. Just to be sure we are not overlooking some issue.\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2785#issuecomment-486985403"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2785#issuecomment-486985403",
"url": "https://github.com/bisq-network/bisq/issues/2785#issuecomment-486985403",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>