Problem monitoring WebSphere/Network Deploy
Having problems getting WebSphere ND monitoring to work. After configuring the AppManager monitor pointing it to the correct perfmon server and deployment manager, not getting any servers listed. perfmon is up and running because when I hit the server w/the correct url, I get an xml file back listing all the servers and PMI data on the PMI-enabled servers.
ApManager logs show
I suspected that something is wrong with the way ApManager tries to collect the data; after sniffing the network traffic between the ApManager and perfmon server I noticed that it's not passing the right URL (see "GET" below)... doesnt look like "host=" followed by the deploymetn manager name is being appended at all. I doublechecked verifying that I do have it configured for the ND environment.
Any idea anyone?
ApManager logs show
java.lang.NullPointerException
at com.adventnet.appmanager.server.datacollection.websphere.WebSphereDataCollector.getCollectedDataThroughServlet(WebSphereDataCollector.java:492)
at com.adventnet.appmanager.server.datacollection.websphere.WebSphereDataCollector.getCollectedData(WebSphereDataCollector.java:761)
at com.adventnet.nms.applnfw.datacollection.server.PerformDataCollection.run(PerformDataCollection.java:86)
at java.lang.Thread.run(Unknown Source)
I suspected that something is wrong with the way ApManager tries to collect the data; after sniffing the network traffic between the ApManager and perfmon server I noticed that it's not passing the right URL (see "GET" below)... doesnt look like "host=" followed by the deploymetn manager name is being appended at all. I doublechecked verifying that I do have it configured for the ND environment.
GET /wasPerfTool/servlet/perfservlet?connector=SOAP&port=8886 HTTP/1.1
Host: crdcasp2app14.inet.nogea.local:9086
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3E
Cookie: JSESSIONID=0000ghgEw3zY5OmQXTCQnQrUnIP:-1
Cookie2: $Version="1"
Accept-Encoding: deflate, gzip, x-gzip, compress, x-compress
HTTP/1.1 200 OK
Server: WebSphere Application Server/5.1
Content-Type: text/html;charset=ISO-8859-1
Content-Language: en-US
Content-Length: 4613
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<h3>PerfServlet Error Page</h3>
<hr>
<b>Using PerfServlet in WebSphere Application Server (single server/base installation):</b><br>
If you are using WebSphere Application Server base installation, use the application server host and connector port.
If additional servers have been created, then use the appropriate server port for which data is required.
PerfServlet will only display data from one server at a time when connecting to WebSphere Application Server.
<p>
<b>Using PerfServlet in WebSphere Application Server - Network Deployment (ND) installation:</b><br>
If you are using to WebSphere Application Server Network Deployment, use the <u>deployment manager</u> host and connector port (see Usage section below).
PerfServlet will display data from all the servers in the cell.
<p>
<b>Usage:</b><br>
http://perfServlet_Host:port/wasPerfTool/servlet/perfservlet?host=<host>&port=<port>&connector=<connector>&username=<username>&password=<password>
<p><b>host</b>
<br>-Default value is 'localhost'
<br>-In base installation use localhost or host where application server is running.
<br>-In Network Deployment installation use <u>Deployment Manager</u> host name<br>
<br><i>Note</i> that there can be more than one server instance in ND installation and PerfServlet can be installed in any one of the servers.
<p><b>port</b>
<br>-Default value is '8880' (SOAP connector port in base installation).
<br>-In base installation use the application server SOAP or RMI connector port.
<br>-In case of Network Deployment installation use <u>Deployment Manager</u> SOAP or RMI port.
<br>-<i>Note</i> that the port numbers for SOAP/RMI connector can be configured in the Administrative Console under Servers - Application Servers - server_name - End Points.
<p><b>connector</b>
<br>-Connector type can be either 'SOAP' or 'RMI'. Default value is 'SOAP'
<p><b>username</b>
<br>-If security is enabled provide the user name
<p><b>password</b>
<br>- If security is enabled provide the password
<p>
For more information refer to the <a href="http://www.ibm.com/software/webservers/appserv/infocenter.html">WebSphere InfoCenter</a>
<p><hr><p>Exception:<br>java.lang.Exception: Error getting WebSphere cell configuration. If you are using to WebSphere Application Server Network Deployment, use the <u>deployment manager</u> host and connector port
.at com.ibm.ws.pmi.perfServlet.PerformanceServlet.doGet(Unknown Source)
.at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
.at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
.at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
.at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
.at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
.at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
.at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
.at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
.at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
.at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1171)
.at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:676)
.at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:203)
.at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
.at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:300)
.at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
.at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:120)
.at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:250)
.at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
.at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
.at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
.at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
.at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Any idea anyone?