You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md.template
+51Lines changed: 51 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -377,6 +377,57 @@ You can find log for running solo command under the directory `~/.solo/logs/`
377
377
The file `solo.log` contains the logs for the solo command.
378
378
The file `hashgraph-sdk.log` contains the logs from solo client when sending transactions to network nodes.
379
379
380
+
## Using Intellj remote debug with solo
381
+
382
+
NOTE: the hedera-services path referenced '../hedera-services/hedera-node/data' may need to be updated based on what directory you are currently in. This also assumes that you have done an assemble/build and the directory contents are up-to-date.
383
+
384
+
Example 1: attach jvm debugger to a hedera node
385
+
```bash
386
+
./test/e2e/setup-e2e.sh
387
+
solo node keys --gossip-keys --tls-keys
388
+
solo network deploy -i node1,node2,node3 --debug-nodeid node2
389
+
solo node setup -i node1,node2,node3 --local-build-path ../hedera-services/hedera-node/data
390
+
solo node start -i node1,node2,node3 --debug-nodeid node2
391
+
```
392
+
393
+
Once you see the following message, you can launch jvm debugger from Intellij
0 commit comments