If that is the way to go i must consider it. Because i do not want to go against the flow.
But actually i solved the problem by adding to line of code to the persistance code. DbPersistenceService.java // added session.flush(); session.clear(); // before transaction.commit(); This seems to help my out of memory. But i havent testet it to death yet. But wat i want to do next is off load the variables to a queue and process it from there. But now i'm first trying to get a grip on the logging. (Now posting a new post about the processInstance id) thx Patrick View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947578#3947578 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947578 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
