Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Performance report subsystem crash with crappy SNMP data in the database

Description

I have seen the OpenNMS performance report subsystem crash with Tomcat Internal
Server Error (500) when there is invalid (as provided by an SNMP agent) data in
the snmpinterface database table (namely the snmpifdescr field). Either, this
data should be corrected before getting into the database or it should be
validated each time it is used by the code, or both...

More details in the following post:
http://lists.opennms.org/pipermail/discuss/2003-April/027452.html

OpenNMS should be immune to any kind of "poison" fed by some crappy SNMP agents.

Environment

Operating System: Windows 2000 Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Former user February 10, 2005 at 1:56 PM

  •  

    •  

      • has been marked as a duplicate of this bug. ***

Former user November 1, 2004 at 6:48 PM

Changed rs.getString("snmpphysaddr").equals(mac) to
mac.equals(rs.getString("snmpphysaddr") since mac is previously checked for null

Former user November 1, 2004 at 6:46 PM

Reference email moved to
http://sourceforge.net/mailarchive/message.php?msg_id=9391871

Fixed this NullPointer exception by ensuring we don't do null.equals(...)

Matt Brozowski

Former user April 8, 2004 at 3:49 PM

Matt to reproduce

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created April 15, 2003 at 12:15 PM
Updated February 10, 2011 at 2:54 PM
Resolved September 9, 2010 at 1:13 PM