It looks like the real issue is in the ActionProcessingPipeline rather than the extendedToString. Looks like there are a number of debug statements being invoked without guards, are they the source of this? If so, a better fix is to add the guards so that they are never invoked unless debugging is enabled (in which case the impact is not so important). Do you have a list of the invocation points within the pipeline? Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269374#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...