[jboss-jira] [JBoss JIRA] Commented: (JBAS-7747) CLONE -Fix oid-sorting in the snmp-adaptor

[Prabhu S (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12515014#action_12515014 ] 

Prabhu S commented on JBAS-7747:
--------------------------------

https://jira.jboss.org/jira/browse/JBAS-3178

In the original bug, the reporter has reported two issues. However, just the first sorting issue has got fixed.

The problem we are facing is this.

* In attributes.xml we have added two entries - 

<mbean name="test:operation=test1,service=Service1" oid-prefix=".1.2.3.4.1.30.1">
        <attribute name="ServiceName" oid=".1" />
        <attribute name="ApiName" oid=".2" />
</mbean>

<mbean name="test:operation=test2,service=Service2" oid-prefix=".1.2.3.4.1.30.2">
        <attribute name="ServiceName" oid=".1" />
        <attribute name="ApiName" oid=".2" />
</mbean>

Now, when we do a snmp walk for oid prefix - .1.2.3.4.1.30, we get the details for just the first MBean alone. This is probably a bug in your tree traversal code, which upon reaching the end node .1.2.3.4.1.30.1.2 thinks thats the end of the MIB. But instead, it should retract back to the node .1.2.3.4.1.30 and traverse the node .1.2.3.4.1.30.2 as well.

Secondly, why is JBoss still using the bogus oid 1.2.3.4? Any plans for using a proper oid prefix. (like  1.3.4.6.1.4.1.18016?)


> 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
>             Fix For: JBossAS-4.2.3.GA, JBossAS-5.1.0.GA, JBossAS-6.0.0.M2
>
>
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira