Return
-
Title
Starting OA getting error about LogManager -
Description
Starting OA the error below might be raised and written in the .err file. However, the OA starts without problem.
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected. -
Cause
Java JDK and/or OpenJDK is missing a class reference or its path. -
Resolution
Solution:
1. From Stat point of view the error might be ignored as more than error it could be consider an annoying warning. To solve the issue:
- On OA machine, edit the statctl.sh file at the 'start' section adding the line signalled below:
print "Starting Stat Oracle Agent for $envCode..."
cd $STAT_JAVA_HOME/bin./java -DSTAT="$envCode" \-Xms256m -Xmx512m \-Dconfigfile=$cfgFile \-Dcmdconfig="$cfgParams" \-DSTAT_HOME=$STAT_HOME \-Djava.util.logging.manager=org.jboss.logmanager.LogManager \ <----- Added line-Dfile.encoding=ISO8859-1 \com.quest.stat.oracle.OAStatAgent $envCode 2>&1 | tee -a $fatalLog &pid=`getPID $envCode`