On Wed, Nov 18, 2009 at 5:29 AM, BluesBrother <j...@objectivelogic.com> wrote: > > Thanks for posting this solution to the OutOfMemory problem. I'm new to > OpenEJB and trying to use it under NetBeans in a unit test scenario. I, too, > was getting the OutOfMemory error, and was clueless as to why. However, > after reading the referenced OpenEJB page, I added an "include" filter > property specifying only the path of my application's classes and voila! > Startup was much faster, I didn't get the OutOfMemory error, and my test > case was executed. Apparently, by default (with no filtering) OpenEJB was > searching for and including every JAR and class it could find! ;-)
It makes two who suffered from it. If it becomes a PITA for more, we'll have to change the approach and search for a very few only with classpath searching disabled (it's nearly impossible to exclude jars from those different envs where OpenEJB could be running within). Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
