Running nodes locally
Starting all nodes at once
runnodesis a shell script (or batch file on Windows) that is generated by
deployNodesto allow you to quickly start up all nodes and their webservers.
runnodesshould only be used for testing purposes.
runnodesby running the following command from the root of the project:
If you receive an
OutOfMemoryError exception when interacting with the nodes, you need to increase the amount of
Java heap memory available to them, which you can do when running them individually. See
Starting an individual Corda node.
Starting an individual Corda node
Run the node by opening a terminal window in the node’s folder and running:
java -jar corda.jar
By default, the node will look for a configuration file called
node.conf and a CorDapps folder called
in the current working directory. You can override the configuration file and workspace paths on the command line (e.g.
./corda.jar --config-file=test.conf --base-directory=/opt/corda/nodes/test).
You can increase the amount of Java heap memory available to the node using the
-Xmx command line argument. For
example, the following would run the node with a heap size of 2048MB:
java -Xmx2048m -jar corda.jar
You should do this if you receive an
OutOfMemoryError exception when interacting with the node.
Optionally run the node’s webserver as well by opening a terminal window in the node’s folder and running:
java -jar corda-webserver.jar
Enabling remote debugging
To enable remote debugging of the node, run the node with the following JVM arguments:
java -Dcapsule.jvm.args="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005" -jar corda.jar
This will allow you to attach a debugger to your node on port 5005.