On May 21, 2013, at 1:11 PM, John D. Ament <[email protected]> wrote:
> aki > > In my case, the request body is too large to show in the debug logging. > That limits it to 64kb. Actually, I think the debug logging defaults to 100K, not 64K. > This is for an outbound web service call we're > making using CXF as our runtime, so I'm not sure how to enable interceptors > that way. How are you turning on the logging? The logging interceptor and feature both have a "limit" property that can be set to something much larger if needed. Dan > > > On Tue, May 21, 2013 at 12:44 PM, Aki Yoshida <[email protected]> wrote: > >> Not sure what is the best approach to suggest, as your question is somehow >> indirect and maybe there is another way to analyze the issue.. >> >> If you are talking about the temporary files that are created during >> processing, you need to write an interceptor to interfere with the normal >> operation of this caching to leave the files undeleted after processing. >> >> If you just want to look at the message content, isn't it easier to >> activate the logging feature? >> >> regards, aki >> >> >> >> 2013/5/21 John D. Ament <[email protected]> >> >>> Hi all >>> >>> I'm currently debugging an issue w/ CXF where fields are coming in wrong >> to >>> our webservice (CXF is the client). I have debug logging turned on but >> the >>> payloads are too large so I can only see the first 64kb of the message. >> Is >>> it possible to have CXF keep the files that it creates rather than >> deleting >>> them? >>> >>> John >>> >> -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
