[SNMP4J] java.io.InterruptedIOException: operation interrupted

[Frank Fock]

OK, then you do not miss any responses. The transport mappings are
implemented independently from the Snmp class. Consequently, the
mappings know nothing about outstanding requests, they always
listen for packets (for example incoming traps). Thus, it is normal
to get this log message on a Snmp.close().

But, since the log level of WARN could be irretating (what your
question proves), I will set the level to INFO for the next release.

Does this explanation help?

Best regards,
Frank

Mathias Bogaert wrote:

> That's exactly what I do. All synchronous requests, and after that, 
> close the transport mapping.
>
> On 24 Sep 2004, at 00:32, Frank Fock wrote:
>
>> Hi Mathias,
>>
>> When you call Snmp.close() you implicitly call close() on all
>> associated transport mappings. Why do you call close() when
>> you have oustanding requests?
>>
>> The only way to assure that you have waited for all time-outs
>> is to use synchronous requests.
>>
>> Best regards,
>> Frank
>>
>> Mathias Bogaert wrote:
>>
>>> Hi,
>>>
>>> When calling close() on the Snmp instance, I frequently get 10466042 
>>> WARN  [Thread-903] (snmp4j.transport.DefaultUdpTransportMapping:193) 
>>> - java.io.InterruptedIOException: operation interrupted.
>>> What exactly does this mean? That the stack is stopping listening 
>>> for any incoming messages? If so, how can I wait for all possibe 
>>> time-outs to occur before closing the stack?
>>>
>>> Thanks,
>>>
>>> Mathias Bogaert
>>>
>>> _______________________________________________
>>> SNMP4J mailing list
>>> SNMP4J at agentpp.org
>>> http://p15141779.pureserver.info/mailman/listinfo/snmp4j
>>>
>>
>>
>>
>>
>
>