[ https://jira.jboss.org/jira/browse/JBAS-7747?page=com.atlassian.jira.plug... ] 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?) -- 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

[ https://jira.jboss.org/jira/browse/JBAS-7747?page=com.atlassian.jira.plug... ] jaikiran pai commented on JBAS-7747: ------------------------------------ Please do not mark the "Fix Versions" when you open a JIRA issue. -- 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

[ https://jira.jboss.org/browse/JBAS-7747?page=com.atlassian.jira.plugin.sy... ] Heiko Rupp commented on JBAS-7747: ---------------------------------- What does the SNMP-Spec say about levels of re-tracking? In the above example - if 1.2.3.4.1.30.1 has been tried and then 1.2.3.4.30.2 and there is no 1.2.3.4.30.3 -- should this go down to 1.2.3.4 and try with sub-node .31? About the 2nd question - you mean within attributes.xml as defaults ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira