Iâve upgraded to agent v1.3 (and AgenPro 2.7.5) and discovered many NPEs in
my application.
The AgenPro generates:
=
private MOScalar myTest;
protected void createMO(..) {
myTest = moFactory.createScalar(oidMyTest,
moFactory.createAccess(..),
null, -- problem. Was: new
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.
(updated wrong subject)
Frank,
My old versions before upgrade were snmp4j-1.11 and snmp4j-agent-1.4
My new versions are snmp4j-2.2.3 and snmp4j-agent-2.0.10a
The line numbers for code in question in
org.snmp4j.agent.DefaultMOServer class:
=== snmp4j-agent-2.0.10a ===
271 public void
I implemented notification 'appShutdown' as follows:
1. NotificationOriginatorImpl -> notify() with 'appShutdown'
notification.
2. Snmp -> close() to release all resources.
3. Close application.
The result is exception (line numbers are for SNMP4J v2.6.2):
java.lang.RuntimeException:
Frank,
Tested and confirmed: v2.7.0 has the issue resolved.
Thanks,
Mark
On 2018-11-15 15:21, Frank Fock wrote:
> Hi Mark,
>
> The following snapshot 2.7.0 release should provide a fix for this
> issue:
>