HP 3PAR Policy Manager Software - Manual (Page 42)

8 Troubleshooting and Maintenance
When Tomcat5 is operating in standalone mode, you may need to troubleshoot for the following
functionality:
Troubleshooting
Solution Problem
Another web server or other
process is operating on port 1. Modify the server.xml file and replace port 8080 with another, unused port greater
than 1024 (because ports of 1024 or less require super user access for binding).
8080, which is the default 2. Restart Tomcat and access it using the new port; for example, http://localhost:1080
or https://localhost:1080 if SSL is enabled. HTTP port that Tomcat attempts
to bind to at startup.
An out of environment space
error is encountered when 1. Open the properties for the StartupAPM.bat file or ShutdownAPM.bat file
and view the Memory tab. In the Initial environment field, enter 4096.
running the startup or startup
2. Click Apply.
Windows creates shortcuts in the directory with which you can start and stop the
container.
scripts on Windows-based
operating systems.
Ensure the proxy settings for your browser are configured such that your browser will
not go through a proxy to access the localhost machine. For Internet Explorer, these
settings are located under Tools
→Internet Options→Connections→LAN Settings.
The localhost machine is not
found. This can happen if your
browser computer is located
behind a proxy server.
Maintaining the Server and Database
Performing maintenance work on the Policy Manager after operations have started is limited to
log file maintenance and configuration file settings.
It is important that you keep track of the number and size of the audit log files created on disk.
You should remove unnecessary files and archive those that are not of immediate need. Also, make
sure you modify the server configuration settings, especially those set in the
PolicyManager.properties
file, as the needs and functionality of your server change.
42 Troubleshooting and Maintenance