[ https://issues.jboss.org/browse/JBTM-2247?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2247: ---------------------------------------- What do you mean by it works - the issue you have reported is that there are so many outstanding resource enlistments that the JVM runs out of memory. Note that this is not a leak in the transaction manager since we are doing what is requested (ie enlisting a resource on each ejb call - the reason we have to store duplicates is that the spec says we need to make the corresponding delist call come commit time). As far as can see, you have 2 options, either increase your heap size or restructure things to avoid making thousands of calls within the same transaction. -- This message was sent by Atlassian JIRA (v6.3.1#6329)