Renato,
No, the concurrent modification exception is probably what happens when
multiple threads attempt to use the wrong port (555555). If one thread
is in the middle of exception processing for the illegal argument any
other threads will get the ConcurrentModificationException, if enough
threads gets started they will also generate timeouts.
It's not an isolated error, it's a continuous cycle of sends in multiple
threads.
Also I agree with Frank that you should upgrade your Java version.
Gene
Renato Araújo Ferreira wrote:
Frank,
I found that someone that configured the system to try to use the
wrong port (555555), but when I solved this error the timeout problem
and the ConcurrentModificationException stopped to ocurr. Is it an
incorrect exception handling of IllegalArgumentException inside the
DefaultUdpTransportMapping? Because an isolated error affect all SNMP
processing of snmp4j in VM.
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
