Forums: Troubleshooting and Problems
Hi David,
The Validator will use whatever version of Java is used when you call the java command from the command line (or by using the check-java.bat script), unless you modify the client.bat file to point to a specific Java instance.
If I remember correctly, there were four releases of the JRE 1.5 that contained a bug that was triggered by the Validator, resulting in extremely slow performance due to the JRE consuming far more resources than allowed. It's possible that you had one of these versions, and upgrading to 1.6 would have resolved the issue. The Validator is only compatible with JRE 1.5 and above, so will fail to launch on an earlier version.
Regards,
Tim
Thanks Tim for the follow-up. Works fine now and I will keep that in mind.
We have OpenCDISC installed and it takes many minutes or never for the OpenCDISC window to appear.
We have JRE 1.6.0_17
Actually, as of now, nothing opens any more.
Can you help?
Tom pineo
Hello,
I am using standard config files and Controlled Term files. Validator works fine until half way through then it grinds to a halt - process 10 records per second.
Turns out it is a Java issue. I had JRE 1.5 on my machine but I also had 1.4_19. When I upgraed to 1.6 the issue is resolved. Does the validator handle multiple versions of JRE on a machine?
David