[SNMP4J] Problem with DefaultTCPTransportMapping

Brice Fines bfines at sermepa.es
Tue Oct 13 12:04:50 CEST 2009


Hi Frank,

Thanks for providing another update so quickly.
I donwloaded and tried the snapshot version dated 12 October 2009 in 
various environments.
As you said, I have no longer to wait for the connection timeout to 
happen, now everything works right.

I think I found another problem, but I will report it in a new thread 
(since this one is about DefaultTCPTransportMapping and you solved the 2 
problems we detected); the new one will be about 
TCPTransportMapping.close(address), but with your last fix in 
DefaultTCPTransportMapping, I do not need to use 
TCPTransportMapping.close(address) anymore.

I hope the DefaultTCPTransportMapping fixes will be included in 1.10.2 
release.
Thanks

Regards


More information about the SNMP4J mailing list