[AGENT++] AgentX++ suagent commiterror let the RowStatus in detroy(6); the row is block forever!

[Claus Klein]

Hi Frank,

I have a big problem with net-snmp as agents master.

I had a look at the if_mib implementation.
But I can not see, where the index is allocated, but this does not  
help anyway.

For some tables I must use shared tables.

The code is generated with AgentPro. What must I add or change to the  
generated code?
I need a simple shared table with rowStatus which works?

Can you send me an example.
I have to find the net-snmp bug.

Best regards,
Claus

On 03.11.2010, at 00:09, Frank Fock wrote:

> Hi Claus,
>
> As the documentation of the AgentXSharedTable points out,
> the allocate_index method has to be called manually
> and it is NOT called by add_row.
>
> The question you probably want to ask is: "Why"?
>
> A shared table does not make sense, if you have a single
> subagent only (as in your test).
> If there are more than one agent, a row creation through
> RowStatus mechanism, cannot work, because for the new
> row, it is unclear which subagent should allocate/register
> the row.
>
> That is the reason, why the allocate_index has not been
> called automatically by add_row (it won't work in real-life
> agents).
>
> Instead, the agentppTestSessionsTable exists that contains
> a row for each subagent session. It provides the means needed
> to be able to create a row in the associated shared table
> on behalf of an user selected subagent.
>
> Consequently, the problem with the agentppTestSharedTable
> implementation is that it allows the createAndWait and
> createAndGo operations (without proper index allocation).
>
> It is not valid to deduce from that table implementation
> on problems with other shared tables.
>
> I will fix the agentppTestSharedTable implementation
> as indicated by the [APP-14] issue.
>
> Best regards,
> Frank
>