uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: How to configure correct JRE path when executing the DocumentAnalyzer?
Date Wed, 14 Nov 2012 13:36:15 GMT

The script you are running, which is failing on the line you noted below, is
attempting to start Java.  The variable $UIMA_JAVA_CALL is set earlier in the
script with this code:

if [ "$JAVA_HOME" = "" ]

This means, if you have an environment variable named JAVA_HOME, it will attempt
to run java from $JAVA_HOME/bin/java.  If that environment variable is not set,
then it will just try calling "java", using the system defaults.

Please try setting $JAVA_HOME so that $JAVA_HOME/bin/java points to a valid
java, or just unset it.
Hope this helps.


On 11/13/2012 10:03 PM, Tony Su wrote:
> System: x64 openSUSE 12.2
> Eclipse: Juno
> Following the YouTube "Running UIMA Tools" video,
> Attempted to run the documentanalyzer script and received an error as
> follows:
> Computer:/apache-uima/bin # ./documentAnalyzer.sh
> /home/tony/apache-uima//bin/runUimaClass.sh: line 109:
> /usr/lib64/jvm-exports/java-1.7.0-openjdk-1.7.0/jre/bin/java: No such file
> or directory
> The affected line of code:
> "-Duima.home=$UIMA_HOME" "-Duima.datapath=$UIMA_DATAPATH"
> "-Djava.util.logging.config.file=$UIMA_LOGGER_CONFIG_FILE" "$UIMA_CVDMAN"
> $UIMA_JVM_OPTS "$LOG4J_CONFIG_FILE" -DUimaBootstrapSuppressClassPathDisplay
> -Dorg.apache.uima.jarpath="$UIMA_CLASSPATH" -jar
> "$UIMA_HOME/lib/uimaj-bootstrap.jar" $@
> It looks to me like the code assumes that the JRE has a  path similar to
> the JDK so constructs an incorrect path.
> Example of JDK path on my system:
> /usr/lib64/jvm-exports/java-1.7.0-openjdk-1.7.0
> Example of JRE path on my system:
> /usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/jre
> You can then compare the incorrect path in the script which largely is
> similar to the path to the jdk
> /usr/lib64/jvm-exports/java-1.7.0-openjdk-1.7.0/jre/bin/java
> So,
> I cannot decipher the affected line of code to know which part even points
> to Java, and I am surprised that since all other Java apps work on this
> machine that somehow this code explicitly describes a JRE path instead of
> simply using system defaults.
> TIA,
> Tony

View raw message