ICE in docs To implement a custom Action Processor, simply implement the org.jboss.soa.esb.actions.ActionPipelineProcessor interface. This interface supports implementation of stateless actions that have a managed lifecycle. A single instance of a class implementing this interface is instantiated on a per pipeline basis (i.e. per action configuration). This means you can cache resources needed by the action in the initialise method, and clean them up in the destroy method. But it means that all threads access action by turns, so it is no synchronization needed? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187989#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...