Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 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
    • Fix Version/s: No Release
    • Component/s: Management services
    • Labels:

      Description

      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".

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pilhuhn Heiko Rupp
                  Reporter:
                  prabhus14 Prabhu S
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: