Hi Mark,
You wrote that you upgraded SNMP4J but quoted SNMP4J-Agent
code. Have updated SNMP4J-Agent as well? To which version?
Why do you think that user (USM user?) contexts are related
to the MOServer.register(..) method?
(I would claim that they are not related)
Best regards,
Frank
Am 25.12.2013 22:15, schrieb [email protected]:
Hi,
I upgraded my working application from SNMP4J v1.11 to v2.2.3...
There were some minor updates required in my code to use generics.
I discovered a serious problem in my code with SNMP4J v2.2.3:
empty default context for v3 user is not allowed any more
if there is a v2 user defined as well.
The problem is in a org.snmp4j.agent.DefaultMOServer class.
The method register(ManagedObject mo, OctetString context) in v2.2.3
makes following validation:
if ((context == null) || (context.length() == 0)) {
} else ...
The v1.11 implementation had
if (context == null) {
} else ...
The v2.2.3 validates default v3 empty context as v2 and
throws DuplicateRegistrationException if v2 user is present.
Am I missing something or this is a bug?
Thanks,
Mark
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
