Return-Path: X-Original-To: apmail-cxf-users-archive@www.apache.org Delivered-To: apmail-cxf-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C0262D462 for ; Tue, 21 May 2013 18:39:18 +0000 (UTC) Received: (qmail 77067 invoked by uid 500); 21 May 2013 18:39:18 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 77024 invoked by uid 500); 21 May 2013 18:39:18 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 77011 invoked by uid 99); 21 May 2013 18:39:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 18:39:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [64.85.173.253] (HELO server.dankulp.com) (64.85.173.253) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 18:39:13 +0000 Received: by server.dankulp.com (Postfix, from userid 5000) id 9024D1835CD; Tue, 21 May 2013 14:38:32 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.dankulp.com X-Spam-Level: X-Msg-File: /tmp/mailfilter-users@cxf.apache.org.I2t5wSy7OF Received: from macbook.house.dankulp.com (c-24-91-72-253.hsd1.ma.comcast.net [24.91.72.253]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.dankulp.com (Postfix) with ESMTPSA id BDF5A1835AC; Tue, 21 May 2013 14:38:27 -0400 (EDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_19D6C81E-94A5-46F2-A85F-E126BBC30428" Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Keep tmp files around From: Daniel Kulp In-Reply-To: Date: Tue, 21 May 2013 14:38:45 -0400 Cc: users@cxf.apache.org Message-Id: <2AC3C8C7-2452-4B29-A657-B5D92FAF0345@apache.org> References: <6C33D265-335D-46FD-8137-CDD6E2639BBB@apache.org> <70C8A5CC-E239-47C6-B510-2B625B0153C5@apache.org> To: John D. Ament X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, HTML_MESSAGE shortcircuit=no autolearn=ham version=3.3.2 --Apple-Mail=_19D6C81E-94A5-46F2-A85F-E126BBC30428 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On May 21, 2013, at 2:35 PM, John D. Ament = wrote: > Daniel, >=20 > Thanks. I added=20 >=20 > @org.apache.cxf.annotations.Logging(limit =3D = Integer.MAX_VALUE,inLocation=3D"file:///tmp/cxf/in.txt",outLocation=3D"fil= e:///tmp/cxf/out.txt") >=20 > 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 >=20 > John >=20 >=20 > On Tue, May 21, 2013 at 2:13 PM, Daniel Kulp wrote: >=20 > On May 21, 2013, at 1:58 PM, John D. Ament = wrote: >=20 > > 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. >=20 > Honestly, no idea on what to do within JBoss. >=20 > You could stick an @org.apache.cxf.annotations.Logging(limit =3D = 100000000) or something annotation on the service interface. That = should do it. Beyond that, you'd likely need to check the JBoss docs. >=20 > Dan >=20 >=20 >=20 > > > > John > > > > > > On Tue, May 21, 2013 at 1:52 PM, Daniel Kulp = wrote: > > > > On May 21, 2013, at 1:41 PM, "John D. Ament" = 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 = wrote: > > > > > >> > > >> On May 21, 2013, at 1:11 PM, John D. Ament = 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 = 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 > > >>>> > > >>>>> 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 > > > > >=20 > -- > Daniel Kulp > dkulp@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >=20 >=20 --=20 Daniel Kulp dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com --Apple-Mail=_19D6C81E-94A5-46F2-A85F-E126BBC30428--