Its been a while since jnetpcap received a refresh and I think one is overdue. I would like to start a discussion on how to proceed with jnetPcap v2.
Here is my response to an article posted by Per-Ake Minborg on Javalobby:
Article link: Enforcing Java Singletons is Very Hard
Here is our recommendation on how to avoid "Out of Memory Exceptions". The newer JVM GC (JRE 6 and 7) utilize parallel GCs which do not work with jNetPcap's DisposableGC. Because of large amount of RAM available in today's systems, it is tempting to increase -Xmx and -Xms parameters to something huge. However this is counter productive and is main reason why OOM messages occur in jNetPcap.
An outstanding issue with IDE environments (Eclipse/NetBeans/etc) is the fact that under IDE environment pressing the "red stop" button to terminate the application while running or debugging causes the process to terminate so abruptly as not to allow java VM hooks to execute and perform the necessary cleanup, among other things. Just look at this Eclipse bug 38016.