[AGENT++] memory limitation (crashes)

[Frank Fock]

Hi Jean-Philippe,

I do not think that it is a stack overflow,
but that should be easy to verify by a stack
dump.

I would guess that it is a race condition.
How do you synchronize the update thread
with the AGENT++ thread pool (requests)?

More comments inline below:

Jacquemin, Jean-Philippe wrote:
> 
> The questions are:
> (1) Could it really be a stack overflow ?? Has someone ever experienced
> it? How to get further information ?

Use core dump to verify it.

> (2) How to reduce the amount of memory used ?

Undef logging. As last resort, use virtual tables instead
of MibTable (thus use MibComplexEntry instead of MibTable).

> (3) Would it be useful to try and adjust the parameter MAX_SNMP_PACKET
> (currently at 4096) ?

I do not think so.

> (4) Why is MAX_SNMP_PACKET defined as 2048 in SNMP++ redefined as 4096
> in AGENT++ ?

Both should be the same (AGENT++ uses SNMP++ definition).
Please upgrade to the latest version, if you have problems
with that.

> (5) Are there other parameters that may influence the memory footprint ?
>  
The default PDU size (number of allowed variables).

Best regards,
Frank

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com