Hi, It seems that you mix up connection oriented communication (TCP) with connection less (UDP). With UDP you will never know if a target port is reachable or if the application listening on the target port is not responding. In both cases you simply wait forever for a response (=timeout).
Thus, there is no need to change SNMP4J. Best regards, Frank Am 15.02.2013 16:30, schrieb vitz me: > I'm a beginner with Java and SNMP and trying to perform simple get requests. > I faced an issue when the connection timeouts seem to still have an effect, > even though the port specified for SNMP connection is closed on the target > host. > Is it possible to somehow process the UdpPortUnreachable (exception) within > snmp4j? So that if the port is closed the timeout setting would not have any > effect. Or what could be a way for getting around this problem? > The only way I could think of was trying to check the port using Java sockets > before even trying to send SNMP requests.. > Thanks. > _______________________________________________ > SNMP4J mailing list > [email protected] > http://lists.agentpp.org/mailman/listinfo/snmp4j -- --- AGENT++ Maximilian-Kolbe-Str. 10 73257 Koengen, Germany https://agentpp.com Phone: +49 7024 8688230 Fax: +49 7024 8688231 _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
