[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: Calling Synchronization.afterCompletion() more than once

[bstansberry@jboss.com]

"mark.little at jboss.com" wrote : "bstansberry at jboss.com" wrote : I'm wondering because I wrote some unit tests that check for classloader leaks following an undeployment.  If transactions are used, test shows reference chains leading back to JBossTS via a Synchronization.  My assumption is JBossTS releases the ref to the Synchronization in some later cleanup task.
  |   | 
  | 
  | What Synchronization? Are you saying that for each transaction, a Synchronization implementation isn't being garbage collected or that other objects from JBossTS aren't being garbage collected? I'm unclear from your description.

Using JBossTS; AS Branch_4_2. The specific Synchronization was org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor$InstanceSynchronization (used in EJB2 SFSBs to clear bean locks).

I'll remove the state-nulling bit I did and re-run the test. That will produce a report showing the reference chain; I'll post it.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028082#4028082

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028082