DualShield is a web based application. It dose require certain time for web server (Tomcat) to be up running. Users can observe CPU usage and performance to check whether DualShield server is fully started.
Open Windows Task Manager, go to the processes tab, and search for DualShield Server on Windows 2012 or tomcat6.exe on Windows 2008:
DualShield Server or tomcat6.exe consumes high CPU usage and memory when DualShield service is initiated. Depending on your server's resources, it may take a few minutes for the DualShield service to be fully started. The distinct sign is that the CPU usage of the DualShield service will instantly drop down to almost 0% and maintain low usage. Once fully started, you can launch the DualShield Management Console to login.
set of JAVA server applications. After the installation, upgrade or restart of the DualShield servers, The OS needs to initialise the JAVA virtual machine (JVM) and load the DualShield application into the JVM. This process can be slow and take a long time, depending on the speed and power of the machine.
To wait for the DualShield server to be fully loaded and monitor the its initialisation progress, launch the Windows Task Manager and check the process called DualShield Server which is often a sub-process of Commons Daemon Service Runner, as shown below:
During the initialisation process, the CPU usage of the DualShield Server process will go up and down, and the Memory consumption will continue to increase.
When the CPU usage drops to zero or slightly above zero, and the memory consumption reaches close to 1.8GB for the backend or 550MB for the frontend, that's the indication that DualShield is fully loaded and ready for operation.