Centralized Management Console inaccessible after commenting the defaults file

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

After commenting the following entries from the file: <Install-Directory>/Web-Servers/Tomcat/Default/conf/web.xml, Centralized Management Console is inaccessible. 

<!--
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
-->

Errors observed on the logs (catalina.log):

<Date & Time> org.apache.coyote.http11.Http11Processor service
SEVERE: Error processing request
java.lang.NullPointerException
        at com.watch4net.apg.v2.gui.tomcat.ForceSSL.invoke(ForceSSL.java:36)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346)
        at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:388)
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:936)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
        at java.lang.Thread.run(Thread.java:750)

<Date & Time> org.apache.coyote.http11.Http11Processor service
SEVERE: Error processing request
java.lang.NullPointerException
        at com.watch4net.apg.v2.gui.tomcat.ForceSSL.invoke(ForceSSL.java:36)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346)
        at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:388)
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:936)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
        at java.lang.Thread.run(Thread.java:750)

 

Environment

All Supported Watch4Net releases

Resolution

Engineering team have notified that disabling these configuration entries is not recommended.

Furthermore, the centralized-management feature has been deprecated, as its functionalities are provided through the Admin UI.
Reference: Link to Centralized-Management in the Admin UI missing on newer versions