Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > SAM JMX monitor throws NullPointerException when monitoring Tomcat Servers

SAM JMX monitor throws NullPointerException when monitoring Tomcat Servers

Updated 8-18-2016

Overview

You may receive NullPointerException errors when monitoring Tomcat Servers using the JMX monitor. When monitoring with the Orion agent for Linux, the JMX monitor requires Java Virtual Machine (JVM) version 1.6 or later.

To resolve, we recommend checking or upgrading your JVM version, upgrade Tomcat if needed, and use the Tomcat Server monitor.

We recommend using the Tomcat Server monitor for monitoring Tomcat Servers. You may need to change your templates and component monitors to use this component monitor type.

Environment

  • SAM 6.3
  • Tomcat Server
  • Orion agent for Linux

 

Cause 

  • JMX monitor requires JVM verion 1.6 or later.
  • Your Tomcat Server version may need to be upgraded.
  • You may be using a JMX monitor for monitoring Tomcat.

 

Resolution

  • Use the Tomcat Server monitor instead of the JMX monitor.
  • Check your product versions and upgrade if needed for JVM and Tomcat Server.
 

 

Last modified

Tags

Classifications

Public