HP 3PAR StoreServ 7400 2-node HP 3PAR Policy Server Administrator's G - Page 81

Appendix A Tomcat Troubleshooting, gateways, HP 3PAR Enterprise Server, Agent Builder

Get HP 3PAR StoreServ 7400 2-node PDF manuals and user guides View all HP 3PAR StoreServ 7400 2-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

Appendix A Tomcat Troubleshooting When Tomcat is operating in standalone mode, you may need to troubleshoot for the following functionality: 1. Another web server or other process is operating on the default HTTP port that Tomcat attempts to bind to at startup (8080). If this is the case, modify server.xml and replace the default port number with another, unused port greater than 1024 (because ports of 1024 or less require super user access to bind to). Then, restart Tomcat and access it using the new port, for example, http://localhost:8081, or https://localhost:8443 if SSL is enabled. 2. The 'localhost' machine is not found. This problem can occur if your browser computer is located behind a proxy server. In this case, make sure the proxy settings for your browser are configured such that your browser does not go through a proxy to access the 'localhost" machine. For Internet Explorer, you can find these settings as follows a. On the Tools menu select Internet Options. b. In the Internet Options dialog box, select the Connections tab. c. In the Connections tab click LAN Settings. The Proxy settings appear in the lower portion of the LAN Settings dialog box. 3. For the Tomcat connector pool, the basic recipe is to keep increasing the limit until your Tomcat has spare threads. That is, the number of active threads is less than the setting for the maxThreads property in the Tomcat server.xml file. (The property for Tomcat's connector thread pool is Server/Service/Connector.maxThreads.) For the database pool, follow this same idea, except that you need to watch for messages saying, "Waiting for a jdbc connection to become available", in the HP3PS log file. Keep increasing the size of the database connection pool until you do not see the messages. This property is in the configuration file for Policy Server, PolicyManager.properties and is called com.axeda.apm.jdbc.max_pool_size. 4. If the external directory server used with Policy Server is restarted or goes offline for any reason, Tomcat looks for a directory server on 'localhost:389'. This is normal Tomcat behavior. Note: Except for operations in SNMP environments, HP 3PAR Policy Server, Policy Agents, Agent gateways, HP 3PAR Enterprise Server, Agent Builder, and Agent Deployment Utility support both IPv4 and IPv6 address formats. For SNMP operations, you must use the IPv4 format (nnn.nnn.nnn.nnn). HP 3PAR Policy Server A-1

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
HP 3PAR Policy Server
A-1
Appendix A Tomcat Troubleshooting
When Tomcat is operating in standalone mode, you may need to troubleshoot for the following
functionality:
1.
Another web server or other process is operating on the default HTTP port that Tomcat attempts to
bind to at startup (8080).
If this is the case, modify
server.xml
and replace the default port number with another, unused port
greater than 1024 (because ports of 1024 or less require super user access to bind to). Then, restart
Tomcat and access it using the new port, for example, http://localhost:8081, or https://localhost:8443
if SSL is enabled.
2.
The ‘localhost’ machine is not found. This problem can occur if your browser computer is located
behind a proxy server. In this case, make sure the proxy settings for your browser are configured
such that your browser does not go through a proxy to access the ‘localhost” machine. For Internet
Explorer, you can find these settings as follows
a.
On the Tools menu select Internet Options.
b.
In the Internet Options dialog box, select the Connections tab.
c.
In the Connections tab click LAN Settings. The Proxy settings appear in the lower portion of the
LAN Settings dialog box.
3.
For the Tomcat connector pool, the basic recipe is to keep increasing the limit until your Tomcat has
spare threads. That is, the number of active threads is less than the setting for the maxThreads
property in the Tomcat server.xml file. (The property for Tomcat's connector thread pool is
Server/Service/Connector.maxThreads.) For the database pool, follow this same idea, except that
you need to watch for messages saying, “Waiting for a jdbc connection to become available”, in the
HP3PS log file. Keep increasing the size of the database connection pool until you do not see the
messages. This property is in the configuration file for Policy Server, PolicyManager.properties and
is called com.axeda.apm.jdbc.max_pool_size.
4.
If the external directory server used with Policy Server is restarted or goes offline for any reason,
Tomcat looks for a directory server on 'localhost:389'. This is normal Tomcat behavior.
Note: Except for operations in SNMP environments, HP 3PAR Policy Server, Policy Agents, Agent
gateways, HP 3PAR Enterprise Server, Agent Builder, and Agent Deployment Utility support both IPv4
and IPv6 address formats. For SNMP operations, you must use the IPv4 format (nnn.nnn.nnn.nnn).