Hi rhh, this looks like a different issue. It is a memory leak and imho has nothing to do with the synchronized TransactionUtil.begin() and commit() methods.
First you have to check out the max heap memory set for JBoss. Look for an option -Xmx256m. Increase it to 1024m. If the test still produces OutOfMemory than there is a memory leak for sure. -- Deyan On Mon, 2010-05-31 at 22:35 -0700, rrhati2010 wrote: > Thanks for the findings and suggestions....even I am facing the same problem > deploying in Jboss4.2 and tested with Jmeter for it's performance. > > Everytime I start putting load on server it gets me Error: OutofMemory or > OutofSwapSpace or Not able to create a new native thread even though there > is enough heap memory(around 512M free). > > I have raised this issue on JIRA also: OFBIZ-3707 > > Further I will try to implement your suggestions and let you know the > results. > > Thanks, > RRH > > > ----- > RRH
