Withdrawal transaction doesn't get tx'ed properly.

[nuschpl]

I have only one peer - local bitcoin core full node.
In Bisq log:

Feb-07 18:34:41.482 [JavaFX Application Thread] INFO o.b.c.TransactionBroadcast: broadcastTransaction: We have 1 peers, adding ed5794a3db232a720ce0b863fbbdea6e53d673edef5d1a39551c997d3b956660 to the memory pool
Feb-07 18:34:41.482 [JavaFX Application Thread] INFO o.b.c.TransactionBroadcast: Sending to 1 peers, will wait for 0, sending to: [127.0.0.1]:8333
Feb-07 18:34:41.485 [JavaFX Application Thread] INFO i.b.c.b.w.WalletService:
sendFunds:
ed5794a3db232a720ce0b863fbbdea6e53d673edef5d1a39551c997d3b956660
updated: 2018-02-07T17:34:41Z
in PUSHDATA(72)[ <!CUT->

ScriptPubKey: CUT Address: CUT
fee 0.00090596 BTC for 783 bytes (115 Satoshi/Byte)
prps USER_PAYMENT

Feb-07 18:34:41.524 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@9d98f480
Feb-07 18:34:41.524 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Sending 5 items gathered from listeners to peer
Feb-07 18:34:41.526 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@c5e736
Feb-07 18:34:41.526 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Sending 1 items gathered from listeners to peer
Feb-07 18:34:41.526 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@dec3a973
Feb-07 18:34:41.527 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Sending 1 items gathered from listeners to peer
Feb-07 18:34:41.527 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@d87a4595
Feb-07 18:34:41.527 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Sending 2 items gathered from listeners to peer
Feb-07 18:34:41.528 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@c2df4bfe
Feb-07 18:34:41.529 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@80911dbe
Feb-07 18:34:41.529 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@57f0d885
Feb-07 18:34:41.530 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@e619ea66
Feb-07 18:34:41.531 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Received getdata message: org.bitcoinj.core.GetDataMessage@563f108f
Feb-07 18:35:10.561 [JavaFX Application Thread] INFO i.b.c.p.p.PriceFeedService: request from provider http://62nvujg5iou3vu3i.onion/ 64.012 sec. after last request

And in Bitcoin core console on localhost:

22:37:20 |   | getmempoolinfo
22:37:20 |   | { "size": 7044, "bytes": 29625414, "usage": 82615920, "maxmempool": 300000000, "mempoolminfee": 0.00000000 }
getmempoolentry ed5794a3db232a720ce0b863fbbdea6e53d673edef5d1a39551c997d3b956660
22:37:37 |   | Transaction not in mempool (code -5)

So transaction seems neither confirmed, nor in mempool and nor expired in mempool.
@cbeams Do you have idea how to debug it further? it may have common reason with non tx'ed transactions during exchange.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.