Data Collector is unable to connect to Managing Server

Technote (troubleshooting)


Problem(Abstract)

The activation of an HTTP Proxy is one possible root cause that prevents DC to communicate with MS in one or both directions.

Symptom

In the SystemErr.log you see messages similar to the ones below:

SystemErr R IPBlockList:adding IP:(...)
...
SystemOut O SMSConfig.initHTTPProxySetting(), Set HTTP proxy host: (...)
SystemOut O SMSConfig.initHTTPProxySetting(), Set HTTP proxy port: 8080
SystemOut O SMSConfig.initHTTPProxySetting(), Set HTTPS proxy host: (...)
SystemOut O SMSConfig.initHTTPProxySetting(), Set HTTPS proxy port: 8080
SystemOut O SMSConfig.initHTTPProxySetting(), Set HTTP non-proxy host (...).*|(...).*|(...).*|(...).*
...


Resolving the problem

As the Managing server host may not be handled by the proxy server, you need to force Data collector to contact MS directly.

This can be done by using the http.nonProxyHosts Java system variable: http.nonProxyHosts=<MSHOST>

So, you can either add the JVM property in the WAS/JVM command line arguments by using the admin console.

-Dhttp.noProxyHosts=<MSHOST>

or by adding a JVM system property through the following page:

Application servers > YOUR-SERVER > Process Definition > Java Virtual Machine > Custom Properties

Name = http.noProxyHosts
Value = <MSHOST>

Restart the application server (DC) after setting the above property.

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Composite Application Manager for Application Diagnostics
ITCAM for APPLICATION DIAGNOSTICS Agent for WebSphere

Software version:

7.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1621436

Modified date:

2014-12-17

Translate my page

Machine Translation

Content navigation