> Hmm, yes, it sounds like there is still a memory leak. I'll take another
I suspect it's a JDK6 bug since I've came across some similar issues googling the internet. I then tried to see if I can reproduce it in JDK5 but I always got a "bad version in class" error, so I assumed that some of our jars must have been compiled under JDK6. Please keep me posted if you have some discovery. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en -~----------~----~----~----~------~----~------~--~---
