[AGENT++] Question about the ::commit_set_request() method

[Fedja Jeleskovic]

While looking at the output from the read-create table, I found that there is a failure in the ::commit_set_request() method (or something that looks like ::commit_set_request2 method) quite often. After looking into this a bit more (in other word playing with debugger) it seem to be due to the wrong index of the table that is passed on. Even though (as you can see in my example below) my index is 4099, it comes in the ::commit_set_request method as zero and it fails as such. Even though agent still does everything that is suppose to do, is there an explanation why this is happening?

Thanks



Fedja Jeleskovic
ps. here is a part of the output:
20050107.15:35:43: 3192: (3)EVENT  : Agent: committing set request: (30)
20050107.15:35:43: 3192: (3)EVENT  : RequestList: finished subrequest (ind)(oid)(val)(syn): (0), (1.3.6.1.4.1.4551.5.1.2.1.1.1.2.1.7.4099), (5), (2)
20050107.15:35:43: 3192: (3)DEBUG  : MibTable: ready_for_service: failed on (col)(value): (1.3.6.1.4.1.4551.5.1.2.1.1.1.2.1.1.4099), (0)
20050107.15:35:43: 3192: (3)EVENT  : Agent: cleaning up set request: (30)