Tomcat
Applications Manager default tomcat is down
If your Tomcat Monitor is down, it could probably be due to changes in Hostname/IP address of the machine in which Applications Manager is installed. You can verify the same using the steps given below: Navigate to ...
Tomcat Manager Application is running, but not accessible from Applications Manager
From tomcat v8 onwards, remote access to Manager Application is disabled by default. You can enable remote access by adding Applications Manager IP address in the RemoteAddrValve. Open the context.xml file located in ...
Data is not being properly populated for Tomcat 5 and above versions in APM. How can I check for correct data?
To check whether data collected properly or not, access the below URLs : For versions below 5.x: http://<Tomcat Host>:<Port>/adventnet/DataServlet For Versions 5.x and above: Server Info: http://<Tomcat ...
How to configure Tomcat Monitor for JBoss 3.2.5?
Steps to configure Tomcat Monitor for JBoss 3.2.5 : 1. Append the following script in the 'web.xml' file, present under 'JBoss_Home\server\deploy\jbossweb-tomcat50.sar\ROOT.war\WEB-INF' folder : <servlet-mapping> <servlet-name>Status ...
I am not able to Monitor Tomcat on HP-UX servers
Reason : The HP-UX machine might have it's own SNMP agent which returns the wrong IP Address during discovery. Solution : Try disabling SNMP Discovery for HP-UX machines. To disable SNMP, refer here.
Some Tomcat 4.x Web applications are not monitored.
Reason: In Tomcat server 4.x, a deployed Web application can be monitored only when web application responds to any query. If there are no requests sent to the Web application, the web application and its servlets cannot be identified and monitored. ...
Discovering Tomcat server fails and it displays "Manageengine Agent has to be deployed for collecting the data from Tomcat Server".
Reason: Tomcat 3.x and 4.x cannot be discovered if Manageengine Agents are not deployed in it. Solution: To discover Tomcat 3.x and 4.x, download Manageengine agents, Tomcat3Agent.zip and Tomcat4Agent.zip respectively, that are bundled with ...
I have multiple Tomcat Servers and also a separate Apache Server running. In this scenario, I'm not able to discover or monitor a Tomcat Server.
Monitoring of Tomcat Server depends on its deployment. This section explains the possible deployment scenarios of Tomcat. Your configuration of host name and the port depends on these scenarios. Also, for Tomcat Server versions 3.x and 4.x, you have ...
In Tomcat monitoring, Applications Manager displays some URLs and applications that are not present in my Tomcat server. Why does this occur ?
In the 4.x and 3.x versions of Tomcat Servers, Applications Manager tracks all the requests that comes to the Tomcat Server and from the requests adds the applications for Tomcat Server. Hence, the random URLs are displayed.
I do not see the "Threads Availability" graph for my Tomcat Monitor.
The data for the "Threads Availability" will be shown only for 5.x version of the Tomcat Server. This data is not available for the 3.x and 4.x version of Tomcat Server.
Applications Manager is not collecting data from Tomcat Server.
If the proxy settings are configured wrong, then Tomcat Data collection will not happen correctly as Applications Manager uses HTTP requests for data collection from Tomcat Server. Check if you are able to access the Tomcat Server from browser in ...
'Manager' application needs to be running in Tomcat server for Applications Manager to collect data from the Server. How can I enable the Manager application?
An application named Manager must be running in Tomcat Server Versions 5.x & above for Applications Manager to monitor the server. By default, this application will be running in the server. To check if it is already running, open the following url ...
When I try to monitor a Tomcat Server of Version 5.x or above, I get the message "Authentication details are wrong".
The following prerequisites must be fulfilled for Applications Manager to monitor Tomcat servers: An application named Manager must be running in Tomcat Server Versions 5.x & above for Applications Manager to monitor the server. By default, this ...