[SNMP4J] DefaultTcpTransportMapping: socket disconnect causes timeouts for all

[Frank Fock]

I used two SNMP4J-Agent Sample Agents and MIB Explorer Pro 4.0 beta
(based on SNMP4J 2.3.0) to reproduce the issue.
I connected to both agents with TCP (by requesting some GET/GETBULK 
requests)
and then killed one of the agent and then send a request to both agents. 
The one
to the killed one timed out and the other work without problems (tried 
several times).

Best regards,
Frank


Am 05.06.2014 15:45, schrieb Ladd:
> Frank Fock <fock at ...> writes:
>
>> Hi Ladd,
>>
>> I cannot reproduce the behavior. Even after killing (-15) one of the
>> agents, the second
>> still works like a charm with the SNMP4J using Oracle JRE 1.7.0_55 on
>> Windows 7 SP 1.
>>
>> Best regards,
>> Frank
>>
> Hi Frank,
>
> That's interesting.  When you suggested a possible JVM bug I tried it here
> on Windows with JRE 1.7.0_51.  I still saw the timeouts to the second agent.
>
> Is your test program small enough to send me?  If I see how you did it I
> might be able to see what I'm doing differently.
>
> Thanks again for the help!
>
> - Ladd
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j

-- 
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax:   +49 7024 8688231