Dear John,

Thanks for rising this issue to us. This issue occurs only latest versions of Windows like Windows 7, 2008 Server etc. It seems that the root cause of this issue lies in the underlying network stack of the Operating System, (ie) the datagram socket becomes unusable randomly and the port is not freed.

We are analyzing this issue and working on to find a solution for this issue, will keep you posted once we find the same.

Meanwhile, could you please test whether this issue occurs in other/older versions of Windows, Linux and update us.


Trust this information is useful.


Regards
Bharatha Selvan.

Thank you for response, this really helps.

We have now seen it on Win7 and Win 2008, we tried running the application in XP compatability mode but problem still occurs.

We don't run/test or qualify on Linux so can't comment.

It is very random, although some of our customer see it quite a bit more than others.

Could one solution be opening a new socket, when this happens and delete the old one ?

I just worry we dont know if we could end up going through 100s of connections or exhausting mem or port resources on OS.

Thanks,

John

Bharatha,

As far as we know, we have never seen this on Windows XP, Vista and 2003, which are the other platforms we test on.

One instance, it takes 4-5 days to manifest itself, on another customer they saw it periodically and restarting the app fixes in, in our other client, restarting the java app that uses the snmp library doesn't help.

Do these problems show up in OpManager as well since it uses the same library ?

We would be very interested in any fixes for this, its becoming a very high visibility issue with our customer.

Thanks,

John

FYI, we found another example of this issue on another forum for SNMP4J, but its suggesting that the root problem maybe  actually Java to Win7 and it is timing related.

http://www.mail-archive.com/snmp4j@agentpp.org/msg01439.html

Bharatha,

This is very hard to reproduce but we have seen this on this platforms running 32 bit java, since our app doesn't run as 64 bit, we dont know if that will fix it.

Thanks,

John

I have just run into this issue in Windows 2008 that wasn't experienced in Windows 2003 or XP.  Application uses SNMP and java.  Restarting the application allows it to work again for another 3-4 days before reoccurring.