Status: Closed (View Workflow)
Affects Version/s: JBossAS-4.2.3.GA
Fix Version/s: 6.0.0.M1
Component/s: SNMP adapter
Similar Issues:Show 9 results
JBAS-2880 EXCEPTION_ACCESS_VIOLATION (0xc0000005) JBAS-1583 Primary key violation on JMS_TRANSACTIONS JBAS-1057 FK Violation deleting 1-1 relationship JBAS-1024 Allow database to throw Referential Integrity violation. JBAS-1098 Foreign key violation during cascade delete JBAS-2056 JMS_TRANSACTIONS constraint violation is not completely fixed JBAS-4609 Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.188.8.131.52 JBAS-526 Conn Mgr closes open connections in violation EJB spec. JBAS-2526 Spec violation: CMP reports tech problem in finder as FinderException
The SnmpAgentService exposes a standard MIB2 System Group. However, the OIDs that are produced violate RFC-1213, which dictates that the sysUpTime value should have a type of TimeTicks. Instead, SnmpAgentService generates a type of int32.
Take the following output from snmpwalk:
SNMPv2-MIB::sysDescr = STRING: Central Computer
SNMPv2-MIB::sysObjectID = OID: SNMPv2-SMI::enterprises.18016.1.1.2
SNMPv2-MIB::sysUpTime = Wrong Type (should be Timeticks): Gauge32: 769331
SNMPv2-MIB::sysContact = STRING: Agent Smith
SNMPv2-MIB::sysName = STRING: firstname.lastname@example.org
SNMPv2-MIB::sysLocation = STRING: In The Matrix
SNMPv2-MIB::sysServices = INTEGER: 64
End of MIB
For systems which monitor SNMP agents (e.g. OpenNMS), this causes them to reject the agent because of the bad type.
The bug lies in org.jboss.jmx.adaptor.snmp.agent.RequestHandlerImpl, which determines the type of the OID value by examining the type of the JMX attribute being monitored. It has no way to generate a TimeTicks value, it can only handle Long, String, Integer and SnmpOID types.
The JBoss wiki states that RFC-1213 is supported, but this is incorrect when the type for sysUpTime is wrong (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSNMPAdapterGetValues). Also the attributes.xml file in xnmp-adaptor.sar quotes RFC-1213.