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

Failure at startup when enabling layered txpool before initial sync done #5636

Closed
fab-10 opened this issue Jun 23, 2023 · 0 comments · Fixed by #5634
Closed

Failure at startup when enabling layered txpool before initial sync done #5636

fab-10 opened this issue Jun 23, 2023 · 0 comments · Fixed by #5634
Assignees
Labels
bug Something isn't working TeamChupa GH issues worked on by Chupacabara Team

Comments

@fab-10
Copy link
Contributor

fab-10 commented Jun 23, 2023

Description

Enabling the layered txpool #5290 before the initial sync is done, causes Besu to fail to start with this error

2023-06-23 12:48:11.172+02:00 | main | INFO  | TransactionPoolFactory | Using layered transaction pool
class org.hyperledger.besu.ethereum.mainnet.feemarket.LegacyFeeMarket cannot be cast to class org.hyperledger.besu.ethereum.mainnet.feemarket.BaseFeeMarket (org.hyperledger.besu.ethereum.mainnet.feemarket.LegacyFeeMarket and org.hyperledger.besu.ethereum.mainnet.feemarket.BaseFeeMarket are in unnamed module of loader 'app')

Workaround until the fix is ready, is to enabled the layered txpool only after Besu is synced.

Steps to Reproduce (Bug)

Start Besu with --Xlayered-tx-pool=true

Frequency: [What percentage of the time does it occur?]
Only when syncing

Versions (Add all that apply)

  • Software version: >= 23.4.1
@fab-10 fab-10 self-assigned this Jun 23, 2023
@fab-10 fab-10 added bug Something isn't working TeamChupa GH issues worked on by Chupacabara Team labels Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working TeamChupa GH issues worked on by Chupacabara Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant