Idea ID 1795401
For larger deployments, a higher capacity trap receiver de-coupled from the main JVM instance would be a welcome improvement. Currently when an NNMi server experiences a rate above 40/second with the default trapFilter.conf file, the JVM garbage collection begins to stutter (S0, S1 nolonger queue and E hits 100) and finally dies. I'm guessing that its single threaded.
I'd like a robust trap receiver that doesn't kill the main application when it experiences difficulty.
Device Support – Monitoring
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.