Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local Tx submission breaks N2C connection #44

Open
nemo83 opened this issue Jan 26, 2024 · 1 comment
Open

Local Tx submission breaks N2C connection #44

nemo83 opened this issue Jan 26, 2024 · 1 comment
Assignees

Comments

@nemo83
Copy link
Contributor

nemo83 commented Jan 26, 2024

Hello,

I've been using Yaci to both listen mempool and submit tx via N2C protocol.

I've been using https://github.com/bloxbean/yaci/blob/main/helper/src/main/java/com/bloxbean/cardano/yaci/helper/LocalTxSubmissionClient.java#L78 to submit Tx, BUT, from time to time, it looks like the response of the tx submission does not get process immediately. It takes another tx submission to get the notification of the previously submitted tx creating a off by 1 callbacks.

This eventually causes the N2C connection to break and makes the mempool monitoring stops as well as stops accepting tx submission.

For testing purposes I've also used the same code BUT using ogmios or submit api to submit TXs, instead of N2C connections and in this case it never breaks, making me thinking that there is a possible issue in the way txs are submitted to local client, possibly the way responses for tx submission are processed.

Please let me know if you need more details!

@nemo83 nemo83 changed the title Tx submission breaks N2C connection Local Tx submission breaks N2C connection Jan 26, 2024
@nemo83
Copy link
Contributor Author

nemo83 commented Jan 31, 2024

Upon suggestions I've instantiated 2 N2C connections:

  1. one for mempool monitoring
  2. one for local n2c tx submission
    Mempool monitoring is now working no problem consistently over several hours, unfortunately the n2c connection used to submit tx seems to have eventually crashed. This is noticeable by the fact that the listener is not being called anymore and no outcome printed in logs.

@satran004 satran004 self-assigned this Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants