You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "John D. Ament" <jo...@gmail.com> on 2013/05/21 16:44:13 UTC
Keep tmp files around
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
Re: Keep tmp files around
Posted by Daniel Kulp <dk...@apache.org>.
On May 21, 2013, at 2:42 PM, "John D. Ament" <jo...@gmail.com> wrote:
> They do, I use CXF annotations in other places.
>
> When I instantiate, all I'm doing is
>
> App a = new App("http://my-host/myservice");
> AppPortType apt = a.getPortType();
> apt.doSomething();
>
> anything special needed?
That should be fine.
That said, if you are doing that, you could also then do:
Client client = ClientProxy.getClient(apt);
client.getOutInterceptors().add(new LoggingOutInterceptor(10000000));
and that should also accomplish what you want.
Dan
>
>
> On Tue, May 21, 2013 at 2:38 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 2:35 PM, John D. Ament <jo...@gmail.com> wrote:
>
>> Daniel,
>>
>> Thanks. I added
>>
>> @org.apache.cxf.annotations.Logging(limit = Integer.MAX_VALUE,inLocation="file:///tmp/cxf/in.txt",outLocation="file:///tmp/cxf/out.txt")
>>
>> To my interface (AppPortType.class). Is there somewhere else it should go?
>
> I believe that should be it. (providing JBoss allows the user application to actually load classes/annotations from the package)
>
> Dan
>
>
>>
>> John
>>
>>
>> On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp <dk...@apache.org> wrote:
>>
>> On May 21, 2013, at 1:58 PM, John D. Ament <jo...@gmail.com> wrote:
>>
>> > Hmmm
>> >
>> > Looking at http://cxf.apache.org/docs/debugging-and-logging.html
>> > I don't see any option to specify the limit. I do see in the code the alternate constructors, but since I'm using JBoss AS 7 and just the JVM option I don't see a way to tell it to use the alternate limit.
>>
>> Honestly, no idea on what to do within JBoss.
>>
>> You could stick an @org.apache.cxf.annotations.Logging(limit = 100000000) or something annotation on the service interface. That should do it. Beyond that, you'd likely need to check the JBoss docs.
>>
>> Dan
>>
>>
>>
>> >
>> > John
>> >
>> >
>> > On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
>> >
>> > On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com> wrote:
>> >
>> > > Currently, I use the JVM option
>> > >
>> > > org.apache.cxf.logging.enabled
>> > >
>> > > and I see this output:
>> > >
>> > > Message (saved to tmp file):
>> > > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
>> > > (message truncated to 65536 bytes)
>> >
>> > Ah. OK. Just looked. The default for the interceptors themselves is 100K, but the LoggingFeature is 64K. The system property uses the LoggingFeature. That explains that.
>> >
>> > Basically, you'll need to do one of:
>> >
>> > 1) Manually configure the logging stuff (see http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the limit appropriately.
>> >
>> > 2) Write an interceptor that would grab the "File" and copy it someplace and configure that in.
>> >
>> > Dan
>> >
>> >
>> >
>> > > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
>> > >
>> > >>
>> > >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
>> > >>>>
>> > >>>>> 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
>> > >> dkulp@apache.org - http://dankulp.com/blog
>> > >> Talend Community Coder - http://coders.talend.com
>> > >>
>> > >>
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org - http://dankulp.com/blog
>> > Talend Community Coder - http://coders.talend.com
>> >
>> >
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Keep tmp files around
Posted by "John D. Ament" <jo...@gmail.com>.
They do, I use CXF annotations in other places.
When I instantiate, all I'm doing is
App a = new App("http://my-host/myservice");
AppPortType apt = a.getPortType();
apt.doSomething();
anything special needed?
On Tue, May 21, 2013 at 2:38 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 2:35 PM, John D. Ament <jo...@gmail.com> wrote:
>
> Daniel,
>
> Thanks. I added
>
> @org.apache.cxf.annotations.Logging(limit = Integer.MAX_VALUE,inLocation="
> file:///tmp/cxf/in.txt",outLocation="file:///tmp/cxf/out.txt")
>
> To my interface (AppPortType.class). Is there somewhere else it should go?
>
>
> I believe that should be it. (providing JBoss allows the user
> application to actually load classes/annotations from the package)
>
> Dan
>
>
>
> John
>
>
> On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> On May 21, 2013, at 1:58 PM, John D. Ament <jo...@gmail.com>
>> wrote:
>>
>> > Hmmm
>> >
>> > Looking at http://cxf.apache.org/docs/debugging-and-logging.html
>> > I don't see any option to specify the limit. I do see in the code the
>> alternate constructors, but since I'm using JBoss AS 7 and just the JVM
>> option I don't see a way to tell it to use the alternate limit.
>>
>> Honestly, no idea on what to do within JBoss.
>>
>> You could stick an @org.apache.cxf.annotations.Logging(limit = 100000000)
>> or something annotation on the service interface. That should do it.
>> Beyond that, you'd likely need to check the JBoss docs.
>>
>> Dan
>>
>>
>>
>> >
>> > John
>> >
>> >
>> > On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
>> >
>> > On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com>
>> wrote:
>> >
>> > > Currently, I use the JVM option
>> > >
>> > > org.apache.cxf.logging.enabled
>> > >
>> > > and I see this output:
>> > >
>> > > Message (saved to tmp file):
>> > > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
>> > > (message truncated to 65536 bytes)
>> >
>> > Ah. OK. Just looked. The default for the interceptors themselves is
>> 100K, but the LoggingFeature is 64K. The system property uses the
>> LoggingFeature. That explains that.
>> >
>> > Basically, you'll need to do one of:
>> >
>> > 1) Manually configure the logging stuff (see
>> http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the
>> limit appropriately.
>> >
>> > 2) Write an interceptor that would grab the "File" and copy it
>> someplace and configure that in.
>> >
>> > Dan
>> >
>> >
>> >
>> > > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org>
>> wrote:
>> > >
>> > >>
>> > >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com>
>> 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 <el...@gmail.com>
>> 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 <jo...@gmail.com>
>> > >>>>
>> > >>>>> 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
>> > >> dkulp@apache.org - http://dankulp.com/blog
>> > >> Talend Community Coder - http://coders.talend.com
>> > >>
>> > >>
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org - http://dankulp.com/blog
>> > Talend Community Coder - http://coders.talend.com
>> >
>> >
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: Keep tmp files around
Posted by Daniel Kulp <dk...@apache.org>.
On May 21, 2013, at 2:35 PM, John D. Ament <jo...@gmail.com> wrote:
> Daniel,
>
> Thanks. I added
>
> @org.apache.cxf.annotations.Logging(limit = Integer.MAX_VALUE,inLocation="file:///tmp/cxf/in.txt",outLocation="file:///tmp/cxf/out.txt")
>
> To my interface (AppPortType.class). Is there somewhere else it should go?
I believe that should be it. (providing JBoss allows the user application to actually load classes/annotations from the package)
Dan
>
> John
>
>
> On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 1:58 PM, John D. Ament <jo...@gmail.com> wrote:
>
> > Hmmm
> >
> > Looking at http://cxf.apache.org/docs/debugging-and-logging.html
> > I don't see any option to specify the limit. I do see in the code the alternate constructors, but since I'm using JBoss AS 7 and just the JVM option I don't see a way to tell it to use the alternate limit.
>
> Honestly, no idea on what to do within JBoss.
>
> You could stick an @org.apache.cxf.annotations.Logging(limit = 100000000) or something annotation on the service interface. That should do it. Beyond that, you'd likely need to check the JBoss docs.
>
> Dan
>
>
>
> >
> > John
> >
> >
> > On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
> >
> > On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com> wrote:
> >
> > > Currently, I use the JVM option
> > >
> > > org.apache.cxf.logging.enabled
> > >
> > > and I see this output:
> > >
> > > Message (saved to tmp file):
> > > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
> > > (message truncated to 65536 bytes)
> >
> > Ah. OK. Just looked. The default for the interceptors themselves is 100K, but the LoggingFeature is 64K. The system property uses the LoggingFeature. That explains that.
> >
> > Basically, you'll need to do one of:
> >
> > 1) Manually configure the logging stuff (see http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the limit appropriately.
> >
> > 2) Write an interceptor that would grab the "File" and copy it someplace and configure that in.
> >
> > Dan
> >
> >
> >
> > > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
> > >
> > >>
> > >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
> > >>>>
> > >>>>> 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
> > >> dkulp@apache.org - http://dankulp.com/blog
> > >> Talend Community Coder - http://coders.talend.com
> > >>
> > >>
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Keep tmp files around
Posted by "John D. Ament" <jo...@gmail.com>.
Daniel,
Thanks. I added
@org.apache.cxf.annotations.Logging(limit =
Integer.MAX_VALUE,inLocation="file:///tmp/cxf/in.txt",outLocation="file:///tmp/cxf/out.txt")
To my interface (AppPortType.class). Is there somewhere else it should go?
John
On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 1:58 PM, John D. Ament <jo...@gmail.com> wrote:
>
> > Hmmm
> >
> > Looking at http://cxf.apache.org/docs/debugging-and-logging.html
> > I don't see any option to specify the limit. I do see in the code the
> alternate constructors, but since I'm using JBoss AS 7 and just the JVM
> option I don't see a way to tell it to use the alternate limit.
>
> Honestly, no idea on what to do within JBoss.
>
> You could stick an @org.apache.cxf.annotations.Logging(limit = 100000000)
> or something annotation on the service interface. That should do it.
> Beyond that, you'd likely need to check the JBoss docs.
>
> Dan
>
>
>
> >
> > John
> >
> >
> > On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
> >
> > On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com>
> wrote:
> >
> > > Currently, I use the JVM option
> > >
> > > org.apache.cxf.logging.enabled
> > >
> > > and I see this output:
> > >
> > > Message (saved to tmp file):
> > > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
> > > (message truncated to 65536 bytes)
> >
> > Ah. OK. Just looked. The default for the interceptors themselves is
> 100K, but the LoggingFeature is 64K. The system property uses the
> LoggingFeature. That explains that.
> >
> > Basically, you'll need to do one of:
> >
> > 1) Manually configure the logging stuff (see
> http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the
> limit appropriately.
> >
> > 2) Write an interceptor that would grab the "File" and copy it someplace
> and configure that in.
> >
> > Dan
> >
> >
> >
> > > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
> > >
> > >>
> > >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com>
> 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 <el...@gmail.com>
> 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 <jo...@gmail.com>
> > >>>>
> > >>>>> 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
> > >> dkulp@apache.org - http://dankulp.com/blog
> > >> Talend Community Coder - http://coders.talend.com
> > >>
> > >>
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: Keep tmp files around
Posted by Daniel Kulp <dk...@apache.org>.
On May 21, 2013, at 1:58 PM, John D. Ament <jo...@gmail.com> wrote:
> Hmmm
>
> Looking at http://cxf.apache.org/docs/debugging-and-logging.html
> I don't see any option to specify the limit. I do see in the code the alternate constructors, but since I'm using JBoss AS 7 and just the JVM option I don't see a way to tell it to use the alternate limit.
Honestly, no idea on what to do within JBoss.
You could stick an @org.apache.cxf.annotations.Logging(limit = 100000000) or something annotation on the service interface. That should do it. Beyond that, you'd likely need to check the JBoss docs.
Dan
>
> John
>
>
> On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com> wrote:
>
> > Currently, I use the JVM option
> >
> > org.apache.cxf.logging.enabled
> >
> > and I see this output:
> >
> > Message (saved to tmp file):
> > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
> > (message truncated to 65536 bytes)
>
> Ah. OK. Just looked. The default for the interceptors themselves is 100K, but the LoggingFeature is 64K. The system property uses the LoggingFeature. That explains that.
>
> Basically, you'll need to do one of:
>
> 1) Manually configure the logging stuff (see http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the limit appropriately.
>
> 2) Write an interceptor that would grab the "File" and copy it someplace and configure that in.
>
> Dan
>
>
>
> > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
> >
> >>
> >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
> >>>>
> >>>>> 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
> >> dkulp@apache.org - http://dankulp.com/blog
> >> Talend Community Coder - http://coders.talend.com
> >>
> >>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Keep tmp files around
Posted by "John D. Ament" <jo...@gmail.com>.
Hmmm
Looking at http://cxf.apache.org/docs/debugging-and-logging.html
I don't see any option to specify the limit. I do see in the code the
alternate constructors, but since I'm using JBoss AS 7 and just the JVM
option I don't see a way to tell it to use the alternate limit.
John
On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com>
> wrote:
>
> > Currently, I use the JVM option
> >
> > org.apache.cxf.logging.enabled
> >
> > and I see this output:
> >
> > Message (saved to tmp file):
> > Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
> > (message truncated to 65536 bytes)
>
> Ah. OK. Just looked. The default for the interceptors themselves is
> 100K, but the LoggingFeature is 64K. The system property uses the
> LoggingFeature. That explains that.
>
> Basically, you'll need to do one of:
>
> 1) Manually configure the logging stuff (see
> http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the
> limit appropriately.
>
> 2) Write an interceptor that would grab the "File" and copy it someplace
> and configure that in.
>
> Dan
>
>
>
> > On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
> >
> >>
> >> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com>
> 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 <el...@gmail.com>
> 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 <jo...@gmail.com>
> >>>>
> >>>>> 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
> >> dkulp@apache.org - http://dankulp.com/blog
> >> Talend Community Coder - http://coders.talend.com
> >>
> >>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: Keep tmp files around
Posted by Daniel Kulp <dk...@apache.org>.
On May 21, 2013, at 1:41 PM, "John D. Ament" <jo...@gmail.com> wrote:
> Currently, I use the JVM option
>
> org.apache.cxf.logging.enabled
>
> and I see this output:
>
> Message (saved to tmp file):
> Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
> (message truncated to 65536 bytes)
Ah. OK. Just looked. The default for the interceptors themselves is 100K, but the LoggingFeature is 64K. The system property uses the LoggingFeature. That explains that.
Basically, you'll need to do one of:
1) Manually configure the logging stuff (see http://cxf.apache.org/docs/debugging-and-logging.html ) and increase the limit appropriately.
2) Write an interceptor that would grab the "File" and copy it someplace and configure that in.
Dan
> On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
>>>>
>>>>> 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
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Keep tmp files around
Posted by "John D. Ament" <jo...@gmail.com>.
Currently, I use the JVM option
org.apache.cxf.logging.enabled
and I see this output:
Message (saved to tmp file):
Filename: /tmp/cxf-tmp-609897/cos8918496558500803807tmp
(message truncated to 65536 bytes)
On Tue, May 21, 2013 at 1:35 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
> >>
> >>> 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
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: Keep tmp files around
Posted by Daniel Kulp <dk...@apache.org>.
On May 21, 2013, at 1:11 PM, John D. Ament <jo...@gmail.com> 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 <el...@gmail.com> 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 <jo...@gmail.com>
>>
>>> 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
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Keep tmp files around
Posted by "John D. Ament" <jo...@gmail.com>.
aki
In my case, the request body is too large to show in the debug logging.
That limits it to 64kb. 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.
On Tue, May 21, 2013 at 12:44 PM, Aki Yoshida <el...@gmail.com> 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 <jo...@gmail.com>
>
> > 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
> >
>
Re: Keep tmp files around
Posted by Aki Yoshida <el...@gmail.com>.
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 <jo...@gmail.com>
> 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
>