SNMP4J-Agent and SNMP4J-Agent-DB 3.3.0 is available for download since 2020-03-04T23:00:00Z. The release fixes several important issues in conjunction with the USM user persistency.
Caution:The protection of rows with a StorageType permanent(4)
is now limited to the RowStatus
destroy(6)
operation which is not allowed. Please check your instrumentation code if you can relax the behaviour that way or if you need to implement your own checks or a readonly(5)
row to fix that issue.
Dependencies
- Java 9 or later
- SNMP4J 3.4.0
- Xodus 1.3.124 (SNMP4J-.Agent-DB only)
CHANGES SNMP4J-Agent 3.3.0
- Fixed [SFJ-196]:
UsmUser
incorrectly removed fromUSM
when restoring agent state after version upgrade from 2.x to 3.x. An affected agent will show aDEBUG
log sequence while restoring agent state as follows:
Updated row…
Adding user…
Removed user with secName=…
Loaded row DefaultMOMutableRow2PC…
A well behaving agent should log this sequence instead:
Updated row…
Adding user… - Added [SFJ-217]: Add
EngineIdProvider
support toEngineBootsCounterFile
. - Fixed [SFJ-219]:
DateAndTime
columnar object’s validate method hides super classmoValidateListener
mechanism. - Fixed [SFJ-220]: Deleting a row using
RowStatus
destroy(6)
withStorageType
permanent(4)
is not rejected.
CHANGES SNMP4J-Agent-DB 3.3.0
- Updated Xodus dependency to 1.3.124, SNMP4J-Agent to 3.3.0, and SNMP4J to 3.4.0.
- Fixed: TLS configuration in sample agent.