TVU output and logging

The following section describes what the Transaction Validator Utility (TVU) outputs to the console, and the options for controlling logging.

By default, the TVU outputs to the console a short summary of what it is doing. If the TVU is run with valid parameters, the output is similar to the following:

Starting
Discovering transactions...
	querying database, all transactions
	transactions found: 8
Processing transactions...

The output is then suspended whilst the transactions are processed, until finally you see, for example:

Processing completed
	transactions expected: 8
	transactions processed: 8
	succeeded: 6
	verification failed: 2
	time taken: 382ms

If a parameter is specified with an incorrect value, the TVU indicates what the problem is, for example:

-t,--load-tx-time: invalid date/time specified. Format should be yyyy-MM-ddThh:mm:ss.nnZ
-e,--error-directory: directory does not exist.
-e,--error-directory: directory is not writeable.

The TVU generates a log file in the current working directory. As with all Corda CLI tools, the level of logging is controlled by the --logging-level parameter. The available levels, in order of increasing detail, are:

  • ERROR
  • WARN
  • INFO (default logging level)
  • DEBUG
  • TRACE

For example:

java -jar transaction-validator.jar --logging-level DEBUG

The --verbose (short version -v) parameter enables verbose logging. This feature takes the messages written to the TVU log file and additionally echoes them to the console.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.