Debugging Besu in IntelliJ - Besu - LF Decentralized Trust


    
        
            
                
                                

        


        
            

            






Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
PreferencesOnly necessaryAccept all









LF Decentralized Trust

LF Decentralized Trust

Spaces

Apps
Templates

Create
























Besu




	All content



Shortcuts



	Meetings

Meetings


 This trigger is hidden

	How-to articles

How-to articles


 This trigger is hidden






Content







Results will update as you type.

	Code of Conduct





	Contributing





	Developing and Conventions




	Besu CLI Style Guide





	Coding Conventions





	Changelog





	Testing





	Debugging Besu in IntelliJ





	Releasing





	Bug Triage Process





	Policies





	Plugin Services





	Tools we use





	Advanced





	Repositories and other projects





	Archive (Dev)





	Changelog Improvement Proposal





	Logging





	Building from source







	Documentation





	Community





	Governance





	Programs & Grants





	Meetings





	Design Documents





	Security





	Audits





	Start Here





	Performance & Stability





	How-to articles





	Incident Reports





	Besu Roadmap & Planning





	How to Contribute



















You‘re viewing this with anonymous access, so some content might be blocked.
Close













Besu

/
Debugging Besu in IntelliJ












More actions







Debugging Besu in IntelliJ

	Sally MacFarlane





Owned by Sally MacFarlane


Jun 04, 2024










Running Besu in debug mode within your IDE can be very useful as this allows you to set breakpoints on certain lines. You can also debug your forked version of the Besu repo in your current branch to confirm the behaviour of any intended changes. To do this in IntelliJ:
	Search for the Besu class (shortcut: command + O and enter ‘Besu’).

	Click on the green triangle to the left of the main method within the Besu class and select Modify Run Configuration to add CLI arguments as you would when running Besu on the terminal. Press apply and OK once done.

	Click on the green triangle again and select Debug ‘Besu.main()’.


Advanced: if you want to debug acceptance tests (that run multiple besu nodes in a cluster), you need to be using ThreadBesuNodeRunner as opposed to ProcessBesuNodeRunner which is the default.
	Otherwise your IDE will not stop at any breakpoints - which is kinda what you want when debugging

	You can set this property acctests.runBesuAsProcess

	or change the code here https://github.com/hyperledger/besu/blob/bdb00b299e2ad8498f9ec70e961774ee0ec9ba9f/acceptance-tests/dsl/src/main/java/org/hyperledger/besu/tests/acceptance/dsl/node/BesuNodeRunner.java#L29









, multiple selections available,





Related content
More info

Collapse
Reporting Bugs
Reporting Bugs

Besu



More like this






Report bugs in the documentation
Report bugs in the documentation

Besu



More like this






Usage of vulnerability scanners
Usage of vulnerability scanners

Besu



More like this






Issues
Issues

Besu



More like this






Logging
Logging

Besu



More like this






Versioned documentation
Versioned documentation

Besu



More like this

































































        

    


    {"serverDuration": 12, "requestCorrelationId": "03922aeeba254119b915bd661a186218"}