It has been pointed out to me that not closing the jbpmSession can be a bad thing in a multithreaded environment. JbpmSession's close method includes a call to popCurrentSession() which should be called or a memory leak may occur.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916751#3916751 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916751 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
