Problem running v1.3 w/ JRE 1.7

f Frank

on March 10, 2014

I'm running OpenCDISC via a BAT file on our compute cluster (OpenCDISC version 1.3, validating define.xml). One of the nodes on the cluster shows the following java -version output:

java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

Another node shows:

java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) Client VM (build 24.51-b03, mixed mode, sharing)
Picked up JAVA_TOOL_OPTIONS: -Djdk.lang.Process.allowAmbigousCommands=true

The program runs fine using 1.5 but crashes noisily with 1.7 (full text is at end of this post).

Is there a known issue w/ OpenCDISC 1.3 - define.xml validation - JRE 1.7? Or might the problem be in the JAVA_TOOL_OPTIONS setting (or something else that can be controlled/configured when I build the BAT file)?

Thanks for your help. Full text of 1.7 errors and messages follows:

08:07:06,863 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
08:07:06,864 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
08:07:06,865 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/S:/Submissions/tools/OpenCDISC/opencdisc-validator-1.3/lib/properties/logback.xml]

08:07:06,990 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attributenot set
08:07:07,000 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender]
08:07:07,007 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ENGINE]
08:07:07,046 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 08:07:07,109 |-INFO in ch.qos.logback.core.FileAppender[ENGINE] - File property is set to [engine.log]
08:07:07,111 |-ERROR in ch.qos.logback.core.FileAppender[ENGINE] - openFile(engine.log,true) call failed. java.io.FileNotFoundException: engine.log (Access is denied)
at java.io.FileNotFoundException: engine.log (Access is denied)
at at java.io.FileOutputStream.open(Native Method)
at at java.io.FileOutputStream.<init>(Unknown Source)
at at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.
java:30)
at at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:163)
at at ch.qos.logback.core.FileAppender.start(FileAppender.java:115)
at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194)
at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180)
at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52)
at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93)
at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52)
at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77)
at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)
at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241)
at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
at at org.opencdisc.validator.settings.ConfigurationManager.<clinit>(ConfigurationManager.java:53)
at at org.opencdisc.validator.DefaultValidator.createManager(DefaultValidator.java:473)
at at org.opencdisc.validator.DefaultValidator.validate(DefaultValidator.java:314)
at at org.opencdisc.validator.cli.CommandParser.parse(CommandParser.java:438)
at at org.opencdisc.validator.cli.Main.main(Main.java:30)
08:07:07,111 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.opencdisc.validator.data.SasTransportDataSource] to OFF
08:07:07,112 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.opencdisc.validator.engine.BlockValidator] to OFF
08:07:07,112 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.opencdisc.validator.settings.ConfigurationManager] to OFF
08:07:07,112 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to OFF
08:07:07,112 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ENGINE] to Logger[ROOT]

The validation has completed.
Picked up JAVA_TOOL_OPTIONS: -Djdk.lang.Process.allowAmbigousCommands=true

Forums: Troubleshooting and Problems

m Michael

on March 10, 2014

Logging

Hi Frank. there are a few issues going on here.

It apprears the error is because one of your nodes doesn't have write access to the engine.log we require: java.io.FileNotFoundException: engine.log (Access is denied)
I would recommend upgrading to the latest OpenCDISC Validator 1.4.1 - this does require at minimum Java 1.6, so i would upgrade your JRE 1.5 on the one node. Regardless, it's good to have both nodes running the same or near same versions of the JRE anyway.

Is there any reason you are still using 1.3 ? As you know the FDA will always run against the latest engine and rules and they maintain that there is no version of quality per say. An issue is an issue, it just may not have been detected in older versions of validator. Although it sounds like the one node might not have write access to your S drive ?? if you can upgrade OCV and your java version to 1.6 on the one node, please try and let us know if the error goes away.