]
jaikiran pai updated JBAS-7747:
-------------------------------
Fix Version/s: (was: JBossAS-4.2.3.GA)
(was: JBossAS-5.1.0.GA)
(was: JBossAS-6.0.0.M2)
CLONE -Fix oid-sorting in the snmp-adaptor
------------------------------------------
Key: JBAS-7747
URL:
https://jira.jboss.org/jira/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, JBossAS-6.0.0.M1, JBossAS-6.0.0.M2
Reporter: Prabhu S
Assignee: Heiko W. Rupp
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.
-
If you think it was sent incorrectly contact one of the administrators: