]
Thomas Hauser commented on JBAS-7747:
-------------------------------------
I have looked into the code that traverses trees in our SNMP adaptor, and currently
GETNEXT requests of a given OID will not leave the subtree of the OID (so an SNMPWALK
1.2.3.4.1.30, which calls GETNEXT successively, upon calling GETNEXT 1.2.3.4.1.30.1.2,
will get the End of MIB you see, Prabhu). I will consult Heiko on what we want to do here,
and we should have a resolution soon.
Thanks,
Tom
CLONE -Fix oid-sorting in the snmp-adaptor
------------------------------------------
Key: JBAS-7747
URL:
https://issues.jboss.org/browse/JBAS-7747
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Management services
Affects Versions: JBossAS-4.2.0.GA, JBossAS-4.2.1.GA, JBossAS-4.2.2.GA,
JBossAS-5.0.0.Beta3, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA,
JBossAS-5.0.0.CR2, JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.Beta1,
JBossAS-5.1.0.CR1, JBossAS-5.1.0.GA, 6.0.0.M1, 6.0.0.M2
Reporter: Prabhu S
Assignee: Heiko Rupp
Labels: jmx, snmp
Sorting of oids still sucks somewhat. Order is currently .1.2.3.1, .1.2.3.10, .1.2.3.2,
.1.2.3.3 which makes getnext return less data than desired
Also take into account, that management systems might ask for a node and then want to
walk the subtree by issuing get and getNext requests. So if a request for a node fails and
this node was no leaf (.0 ending), try to get the subnode with the smallest
"sub-oid".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: