Forums: Troubleshooting and Problems
Hi,
What this usually means is that you're running multi-threaded and there was an exception thrown while validating those particular datasets. Admittedly this behaviour isn't ideal, since you'd expect to get the exception dialog as you would when running single-threaded. I'll look into fixing this.
As far as tracking down the exception goes, you can enable logging in lib/properties/logback.xml. With the Validator not running, change the level in the following line to ERROR:
<logger name="org.opencdisc.validator.engine.BlockValidator" level="OFF" />Then when you run the Validator, any exceptions that get thrown should be logged to the engine.log file in the root Validator directory. Once you've found out what the exception is, please let us know and we'll help you debug further.
Given that things worked fine in your other environments, there's a chance that the problem was the Validator running out of memory. If that ends up being the case, you'll want to increase the memory allowances as described in the Performance and Scalability Guide if possible.
Regards,
Tim