"JAVA_OPTS=" statements keeps getting appended to the Tomcat4.conf file

  • 7001977
  • 21-Nov-2008
  • 26-Apr-2012

Environment

Novell Access Manager 3 Linux Novell Identity Server
Novell Access Manager 3 Java Agents
Novell Access Manager 3 Linux Access Gateway
Novell Access Manager 3 Support Pack 4 applied

Situation

After applying Access Manager 3 Support Pack 4 to a working Access Manager environment, the output of the 'ps aux|grep -i java' command shows that many of the command line parameters were being displayed over and over again. Looking at the /etc/opt/novell/tomcat4/tomcat4.conf file, the reason for this became apparent - many of the command line statements were repeated. The following is an example from one such setup (snippet from end of file):
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS} -Dsun.net.client.defaultConnectTimeout=29000
-Dsun.net.client.defaultReadTimeout=28000 -Dnids.freemem.threshold=10"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_ENDORSED_DIRS="/var/opt/novell/tomcat4/common/nesp-priority/:${JAVA_ENDORSED_DIRS}"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"
JAVA_OPTS="${JAVA_OPTS}
-Daxis.EngineConfigFactory=com.novell.nidp.liberty.wsf.axis.NIDPAxisEngineConfigFactory"


Resolution

Apply SP4 IR1 of Access Manager. These statements are written to the tomcat4.conf file on installation. On the Linux Access Gateway, the lagconfigure.sh is calling the /opt/novell/nesp/bin/config.sh (writes the entries to tomcat4.conf) without checking to see if it's a new installation or an upgrade. We now differentiate between the two.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.