Simple solution is to a) make each hedwig test fork a new jvm and b) increase the max heap
The later asserts are probably due to the earlier direct memory issues. they're in the same test. -Ivan On 25 Mar 2012, at 14:40, Flavio Junqueira wrote: > I was wondering about how to fix the direct buffer memory issue we are seeing > on hedwig server tests running on jenkins: > > https://builds.apache.org/job/bookkeeper-trunk/426/#showFailuresLink > > Note that another issue popping up in some tests is an assertion failure and > not an out of memory issue, like with this one: > > > https://builds.apache.org/job/bookkeeper-trunk/org.apache.bookkeeper$hedwig-server/426/testReport/junit/org.apache.hedwig.server.integration/TestHedwigHub/testServerFailoverPublishOnly_1_/ > > -Flavio >
