[snmp] SNMP v3 discovery bug in 5.1

Birgit Arkesteijn birgit at westhawk.co.uk
Mon Sep 17 16:18:51 BST 2007


Hi Josh,

I made the two changes to the stack and checked them in to cvs on 
SourceForge:
UsmDiscoveryBean.java - new revision: 1.20
SnmpContextv3Basis.java - new revision: 3.14

I tested that normal SNMPv3 requests still work OK.

I'm a little uncomfortable running your TestSnmpV3DiscoveryBug.java on 
my development system, with bringing interfaces up and down and 
(dis)connecting network cables.

Would you mind testing the changes yourself?

Thanks, Birgit

On 17/09/07 14:06, Birgit Arkesteijn wrote:
> Hi Josh,
> 
> I agree with you (and Tim) that option 1 seems better, i.e.
> "Move discovery in front of calling super.addPdu that way an exception
> will not result in a tied up transmitter in the context."
> 
> As to
> "Why isn't the DiscoveryBean using the context pool mechanism and 
> creating its own context directly?"
> I think that's a good point as well. It really should use the pool.
> 
> I'll start working on it. However, I'm not sure how much time I'll have 
> to change & test the code. Next week I'm off for two weeks.
> 
> Oh, and thanks for the good detective work!
> 
> Cheers, Birgit
> 

-- 
-- Birgit Arkesteijn, birgit at westhawk.co.uk,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- Company no: 1769350
-- Registered Office:
-- 15 London Road, Stockton Heath, Warrington WA4 6SJ. UK.
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>


More information about the snmp mailing list