anonymous wrote : I also got stuck in a situation where some code I inherited, a jBPM ActionHandler, used Seam's ComponentgetInstance(...) to look up a SFSB and/or SLSB and invoke a method. In this case, we were regularly having issues with Seam trying to close managed resources - NO TRANSACTION exceptions. Was this ActionHandler a Seam component? Again, I don't understand the scenario, nor why Seam was trying to close transactions that don't exist. Sounds very strange to me. The issue that I do know of is this one: http://jira.jboss.org/jira/browse/JBSEAM-798 And that is, clearly, a bug in Seam's jBPM integration, and one I plan to fix when I get time. There is a workaround, so it doesn't seem like any kind of blocker... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029877#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...