[SNMP4J] EngineID problem

[Mark Gorokhov]

Steps to reproduce the problem:
1. Start application with SNMP4J agent with EngineID
"00:00:00:00:00:00:00:00:02"
2. MIB browser displays managed objects from the application.
3. Close the application (not kill!) This will create SNMP4J persistency
storage.
4. Start the same application with modified EngineID
"00:00:00:00:00:00:00:00:03"
PROBLEM: MIB browser timeouts to display managed objects from the
application.

The problem is fixed after persistency storage is deleted.

How to load SNMP4J persistency storage and not to break EngineID?

-mg