Hi Steffen,
OK, I understand the difference. Nevertheless, the current snapshot already
fixes this issue too.
Although SNMP4J TableUtils could probably handle this kind of scenario smarter,
the scenario you describe is very rare:
1. You configured max-rep-count*max-bindings = 6 > max columns (=
Hi!
> However the problem you described should not happen with a static (unchanged)
> table, because of the inner logic of TableUtils.
I'm sorry, but I still believe I was unable to make the problem clear. You
wrote, this problem should not appear in tables that don't change OR it may
appear w
