Java Web Console Troubleshooting

Cannot Install the Java Web Console

Symptom: at the end of the installation, a message states that the Java Web Console cannot start because there are no registered applications.

Possible causes: once Desktop Manager module is installed, it starts the Java Web Console.

Connection Refused

Symptom: you try to open the appropriate URL, for example https://<your.server>:6789, but the connection is refused.

Possible causes: the Java Web Console is not running on the server.

Cannot Log In

By default, the LDAP login module is not installed. As a result, login credentials are not compared to the ones stored in the LDAP server and only normal system logon credentials are required. This troubleshooting section only applies if you manually installed the LDAP login module.

Symptom: you reach the login page of the Web Console, but the user/password combination is rejected.

Possible causes:

• LDAP server is not running.

• Web Console LDAP authentication module is configured incorrectly

• User does not exist on the LDAP server.

• User has a different password on the LDAP server.

No Desktop Manager Link

Symptom: you log in to the Web Console, but the application list page does not contain the Desktop Manager.

Possible causes:

• Desktop Manager module is not installed

Null Pointer Exception, Tomcat/Java Error or Blank

Symptom: you open the Desktop Manager but nothing of value is displayed, just a blank page or some errors.

Possible causes: if the error mentions NoClassDefFoundError: sun/tools/javac/Main, the Java Web Console is using the wrong Java installation.

Other Issues

If the web server is not performing properly, the log files may provide information. They are located at /var/log/webconsole/. You can increase the log detail level by using smreg:

smreg add -p debug.trace.level=3
smreg add -p debug.trace.options=tmp

The original settings can be restored by:

smreg add -p debug.trace.level=0
smreg add -p debug.trace.options=m

A full dump of the configuration database is triggered by:

smreg list

It is possible that the web server hosting the Desktop Manager may not shut down correctly, leaving its ports in use. This prevents a newly started web server from starting at all. If the smcwebserver start/restart command issues an error messages, or if the Desktop Manager is still accessible even after a smcwebserver stop, or if the newly started server still behaves like the old instance, check if either port 6789 is still in use (netstat -a | grep 6789) or if the web server is still running (ps -ef | grep java). If the one or the other is the case, the according process should be killed and the port 6789 is not in use anymore.