Also, I can eliminate the classloader leak by clearing state in the synchronization's
afterCompletion(), so that tells me afterCompletion() is being invoked; i.e. it's not
a case of a tx not being committed/rolled back.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028122#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...