Stuck during Default configuration

[xrasschaert]

I am running Tomcat7 with java 7 (6 and 8 have same problem) and openAM 12 (13 has same problem)
My problem is very similar to https://forgerock.org/topic/openam-12-0-0-installation-hangs-up/

The OpenAm WAR is deployed and Tomcat starts successfully. I choose the default configuration. The feedback in the GUI is the following:

Checking license acceptance...License terms accepted.
Checking configuration directory /usr/share/tomcat7/openam....Success.
Installing OpenAM configuration store...Success RSA/ECB/OAEPWithSHA1AndMGF1Padding.
Extracting OpenDJ, please wait...Complete
Running OpenDJ setupSetup command: --cli --adminConnectorPort 4444 --baseDN dc=openam,dc=forgerock,dc=org --rootUserDN cn=Directory Manager --ldapPort 50389 --skipPortCheck --rootUserPassword xxxxxxx --jmxPort 1689 --no-prompt --doNotStart --hostname openam.just.fgov.be 
See /tmp/tomcat7-tomcat7-tmp/opendj-setup-4946721296186905806.log for a detailed log of this operation.
Configuring Directory Server ..... 

The OpenAm installation is stuck there and runs forever. I followed the https://backstage.forgerock.com/#!/docs/openam/12.0.0/install-guide installation guide to set the correct java options and file descriptors. I cannot see any warning/error in the log files.

Help is much appreciated.

[Scott Heger]

The biggest thing that causes the install to hang is the lack of setting the “-XX:MaxPermSize=256m” JVM option. But you said you did that. To be sure, can you post the “ps -ef” output of your running tomcat process? That will show all the options tomcat is using.

Aside from that, what OS are you running? Do you have any local firewall running that may be interfering? Also, check the log files of the configuration directory to see if you see anything going on in there.

[xrasschaert]

output ps-ef for tomcat7:
tomcat7 15195 1 11 15:51 ? 00:03:25 /opt/jdk1.7.0_80/bin/java -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -server -XX:MaxPermSize=512m -Xmx3072m -XX:+UseConcMarkSweepGC -Xmx2048m -XX:MaxPermSize=256m -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp org.apache.catalina.startup.Bootstrap start

OS: Debian x86
No local firewall as I’m aware off.
The openam folder only created the opends folder and it’s contents in the installation process. There are no logs inside /openam/opends/logs

[xrasschaert]

I cleaned up my environment variables: the output is now:

/opt/jdk1.7.0_80/bin/java -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -server -XX:MaxPermSize=512m -Xmx3072m -XX:+UseConcMarkSweepGC -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp org.apache.catalina.startup.Bootstrap start

Thank you for your reply

[Scott Heger]

Ok. After the cleanup is the problem still occurring?

[xrasschaert]

Unfortunately, yes it is.

• This reply was modified 6 years, 2 months ago by xrasschaert.

[xrasschaert]

In the log I see that the following lines are repeated indefinitly:

Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: ERROR: The detected Java version could not be used with the set of Java
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: arguments -Xmx0m.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: The detected Java binary is:
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: /opt/jdk1.7.0_80/jre/bin/java
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: You must specify the path to a valid Java 6.0 update 10 or higher version.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: The procedure to follow is:
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: 1. Delete the file /usr/share/tomcat7/openam/opends/lib/set-java-home if it exists.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: 2. Set the environment variable OPENDJ_JAVA_HOME to the root of a valid
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: Java 6.0 installation.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: If you want to have specific Java settings for each command line you must
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: follow the steps 3 and 4.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: 3. Edit the properties file specifying the Java binary and the Java arguments
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: for each command line. The Java properties file is located in:
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: /usr/share/tomcat7/openam/opends/config/java.properties.
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: The output: 4. Run the command-line /usr/share/tomcat7/openam/opends/bin/dsjavaproperties
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: returnCode: 1
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: supported: false
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: Checking if options -Xmx0m are supported with java home: /opt/jdk1.7.0_80/jre
Jun 15, 2016 9:08:30 AM org.opends.quicksetup.util.Utils supportsOption
INFO: launching [/usr/share/tomcat7/openam/opends/lib/_script-util.sh] with env: {OLDPWD=/tmp/tomcat7-tomcat7-tmp, JAVA_HOME=/opt/jdk1.7.0_80, SHLVL=1, LANGUAGE=en_US:en, _SYSTEMCTL_SKIP_REDIRECT=true, JSSE_HOME=/opt/jdk1.7.0_80/jre/, XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, SCRIPT_UTIL_CMD=set-full-environment-and-test-java, PATH=/bin:/usr/bin:/sbin:/usr/sbin, TOMCAT7_USER=tomcat7, PWD=/var/lib/tomcat7, JAVA_OPTS=-Djava.awt.headless=true -server -XX:MaxPermSize=512m -Xmx3072m -XX:+UseConcMarkSweepGC, CATALINA_HOME=/usr/share/tomcat7, CATALINA_TMPDIR=/tmp/tomcat7-tomcat7-tmp, HOME=/usr/share/tomcat7, OPENDJ_JAVA_ARGS=-Xmx0m, CATALINA_PID=/var/run/tomcat7.pid, OPENDJ_JAVA_HOME=/opt/jdk1.7.0_80/jre, _=/usr/share/tomcat7/bin/catalina.sh, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, CATALINA_BASE=/var/lib/tomcat7, LANG=en_US.UTF-8, TOMCAT7_GROUP=tomcat7}

[xrasschaert]

I installed tomcat8 and now I only get one line in my log:

category=QUICKSETUP seq=50 severity=INFO msg=QuickSetup application launched June 15, 2016 11:11:18 AM CEST

[bertalanvoros]

Hello,

I had similar issues when the VM I was running it on didn’t have enough resources.
In my case a VM with a single CPU and 1GB of ram wasn’t enough.
Now the VM running OpenAM has 2 CPUs and 4GB of RAM.

[xrasschaert]

I tried with -Xmx4096m -XX:MaxPermSize=256.
Same problem persists.

[xrasschaert]

The server runs in VM with CPU:

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz
stepping : 11
microcode : 0xbc
cpu MHz : 1866.666
cache size : 4096 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon pebs bts nopl tsc_reliable nonstop_tsc aperfmperf pni ssse3 cx16 x2apic hypervisor lahf_lm dtherm
bogomips : 3733.33
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:

[bertalanvoros]

How many CPUs and how much memory does the vm have?
Is tomcat running on Linux in a VM or on a physical host?

[xrasschaert]

The problem was resolved with a system reboot.
There was a process running in the background (not visible in htop) hogging all the resources.

Thank you for the kind support

[Author]

Posts