Hello Romain, Finally, I used to manage this. I just forgot to update the line 16 of the logging.properties file: add 5request-dumper.org.apache.juli.FileHandler in the list :-(
So the request-dumper file is created :-) but I was not able to see the body of the HTTP requests even if I changed the level to FINE. Any idea to see the HTTP body using this way ? additional configuration ? Best Regards. -----Original Message----- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: mardi 13 décembre 2016 15:01 To: users@tomee.apache.org Subject: Re: [+SPAM+]: Re: Rest payload logging 2016-12-13 14:13 GMT+01:00 COURTAULT Francois < francois.courta...@gemalto.com>: > Hello, > > I have performed several tests: > 1) Added in the logging.properties file, the following lines: > 5request-dumper.org.apache.juli.FileHandler.level = INFO > 5request-dumper.org.apache.juli.FileHandler.directory = > ${catalina.base}/logs > 5request-dumper.org.apache.juli.FileHandler.prefix = request-dumper. > 5request-dumper.org.apache.juli.FileHandler.formatter = org.apache.juli. > VerbatimFormatter > > org.apache.catalina.filters.RequestDumperFilter.level = INFO > org.apache.catalina.filters.RequestDumperFilter.handlers = > 5request-dumper.org.apache.juli.FileHandler > > 2) Then change the FileHandler by.AsyncFileHandler > > 3) Then change the level to FINE > > None of these changes has created a request-dumper log file in the > logs directory :-( Should it be possible that this is because I have > ordered this filter at 5th position ? > > we agree 5request-dumper.* doesnt mean 5th position right? (think it is a "no luck sample" case but just to be sure) Worse case put a breakpoint in it and your endpoint. If from your endpoint you dont see the filter in the stack then it is not well configured. > Best Regards. > > -----Original Message----- > From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > Sent: mardi 13 décembre 2016 10:35 > To: users@tomee.apache.org > Subject: [+SPAM+]: Re: Rest payload logging > > did you configure the logger in info level? > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog < > https://blog-rmannibucau.rhcloud.com> | Old Blog < > http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> > | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > | < > https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-12-13 10:30 GMT+01:00 COURTAULT Francois < > francois.courta...@gemalto.com>: > > > Hello Romain, > > > > BTW, I have checked also the Tomcat 8.5.x documentation at > > https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html > > and the Request Dumper Filter is still there. > > > > So any idea why it hasn't work for me ? > > > > Best Regards. > > > > -----Original Message----- > > From: COURTAULT Francois > > Sent: mardi 13 décembre 2016 10:10 > > To: users@tomee.apache.org > > Subject: RE: Rest payload logging > > > > Hello Romain, > > > > I have added > > org.apache.openejb.cxf.bus.features=org.apache.cxf.feature.LoggingFe > > at ure in the TomEE system.properties file and I am able to see the > > incoming request and the outgoing response. > > > > Thanks for your help. > > > > Best Regards. > > > > -----Original Message----- > > From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > > Sent: lundi 12 décembre 2016 22:02 > > To: users@tomee.apache.org > > Subject: Re: Rest payload logging > > > > it is really just one line to put in conf/system.properties (or jvm > > system > > properties) -> > > https://github.com/tomitribe/tribestream-api-registry/blob/ > > master/tribestream-api-registry-webapp/pom.xml#L365 > > > > If it doesnt work it means your CMD_LINE_ARGS is not used > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog < > > https://blog-rmannibucau.rhcloud.com> | Old Blog < > > http://rmannibucau.wordpress.com> | Github > > <https://github.com/rmannibucau> > > | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE > > | Factory < > > https://javaeefactory-rmannibucau.rhcloud.com> > > > > 2016-12-12 21:51 GMT+01:00 Steve Goldsmith <sgj...@gmail.com>: > > > > > Why not use a logger as I described before? Here's an example if > > > logging client requests > > > https://github.com/sgjava/jcache-tomee/blob/master/src/ > > > main/java/com/codeferm/jcache/tomee/ClientRequestLoggingFilter.jav > > > a > > > > > > On Mon, Dec 12, 2016 at 3:40 PM, COURTAULT Francois < > > > francois.courta...@gemalto.com> wrote: > > > > > > > Hello, > > > > > > > > Change the line 48 of startup.bat from set CMD_LINE_ARGS= to set > > > > CMD_LINE_ARGS=-Dorg.apache.openejb.cxf.bus.features=org. > > > > apache.cxf.feature.LoggingFeature > > > > > > > > And still nothing in catalina log file :-( > > > > > > > > Best Regards. > > > > > > > > -----Original Message----- > > > > From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > > > > Sent: lundi 12 décembre 2016 14:13 > > > > To: users@tomee.apache.org > > > > Subject: RE: Rest payload logging > > > > > > > > Le 12 déc. 2016 14:01, "COURTAULT Francois" > > <Francois.Courtault@gemalto. > > > > com> a écrit : > > > > > > > > Hello Romain, > > > > > > > > Any idea why the solution described at: I have followed this > > > > link http://tomcat.apache.org/ tomcat-7.0-doc/config/filter. > > > > html#Request_Dumper_Filter > > > > doesn't work for me ? > > > > > > > > Check to do is tomcat 8.5 doc for tomee 7. > > > > > > > > > > > > BTW I have added in my REST service endpoint: > @Features(features="org. > > > > apache.cxf.feature.LoggingFeature") thanks to your advice ( > > > > http://cxf.apache.org/docs/features.html) but I haven't found > > > > any HTTP request in all the files located at <TOMEE_HOME>/logs folder: > > > > any > > idea ? > > > > > > > > > > > > It is in catalina.log normally. try putting it in dystem > > > > properties as mentionned. > > > > > > > > > > > > Best Regards. > > > > > > > > -----Original Message----- > > > > From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] > > > > Sent: lundi 12 décembre 2016 09:40 > > > > To: users@tomee.apache.org > > > > Subject: Re: Rest payload logging > > > > > > > > Hi > > > > > > > > cxf built-in solution is to use logging feature: > > > > > > > > org.apache.openejb.cxf.bus.features = org.apache.cxf.feature. > > > > LoggingFeature > > > > > > > > > > > > Romain Manni-Bucau > > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog < > > > > https://blog-rmannibucau.rhcloud.com> | Old Blog < > > > > http://rmannibucau.wordpress.com> | Github <https://github.com/ > > > rmannibucau > > > > > > > > > | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE > > > > | Factory < > > > > https://javaeefactory-rmannibucau.rhcloud.com> > > > > > > > > 2016-12-12 9:31 GMT+01:00 COURTAULT Francois > > <Francois.Courtault@gemalto. > > > > com > > > > >: > > > > > > > > > Hello everyone, > > > > > > > > > > I would be pleased to see the REST HTTP request payload and > > > > > the REST HTTP response payload. > > > > > > > > > > I have followed this link http://tomcat.apache.org/ > > > > > tomcat-7.0-doc/config/filter.html#Request_Dumper_Filter but it > > > > > doesn't work. > > > > > Indeed, I wasn't able to see any request-dumper.log file > > > > > created :( > > > > > > > > > > Is this the good way to achieve this or does it exist others > > > > > solutions > > > ? > > > > > > > > > > Best Regards. > > > > > ________________________________ This message and any > > > > > attachments are intended solely for the addressees and may > > > > > contain confidential information. Any unauthorized use or > > > > > disclosure, either whole or partial, is > > prohibited. > > > > > E-mails are susceptible to alteration. Our company shall not > > > > > be liable for the message if altered, changed or falsified. If > > > > > you are not the intended recipient of this message, please > > > > > delete it and notify the > > > > sender. > > > > > Although all reasonable efforts have been made to keep this > > > > > transmission free from viruses, the sender will not be liable > > > > > for damages caused by a transmitted virus. > > > > > > > > > ________________________________ This message and any > > > > attachments are intended solely for the addressees and may > > > > contain confidential information. Any unauthorized use or > > > > disclosure, either whole or partial, is > prohibited. > > > > E-mails are susceptible to alteration. Our company shall not be > > > > liable > > > for > > > > the message if altered, changed or falsified. If you are not the > > > > intended recipient of this message, please delete it and notify > > > > the > > sender. > > > > Although all reasonable efforts have been made to keep this > > > > transmission free from viruses, the sender will not be liable > > > > for damages caused by a transmitted virus. > > > > ________________________________ This message and any > > > > attachments are intended solely for the addressees and may > > > > contain confidential information. Any unauthorized use or > > > > disclosure, either whole or partial, is > prohibited. > > > > E-mails are susceptible to alteration. Our company shall not be > > > > liable > > > for > > > > the message if altered, changed or falsified. If you are not the > > > > intended recipient of this message, please delete it and notify > > > > the > > sender. > > > > Although all reasonable efforts have been made to keep this > > > > transmission free from viruses, the sender will not be liable > > > > for damages caused by a transmitted virus. > > > > > > > > > > > > > > > > -- > > > Steven P. Goldsmith > > > > > ________________________________ > > This message and any attachments are intended solely for the > > addressees and may contain confidential information. Any > > unauthorized use or disclosure, either whole or partial, is prohibited. > > E-mails are susceptible to alteration. Our company shall not be > > liable for the message if altered, changed or falsified. If you are > > not the intended recipient of this message, please delete it and > > notify the > sender. > > Although all reasonable efforts have been made to keep this > > transmission free from viruses, the sender will not be liable for > > damages caused by a transmitted virus. > > > ________________________________ > This message and any attachments are intended solely for the > addressees and may contain confidential information. Any unauthorized > use or disclosure, either whole or partial, is prohibited. > E-mails are susceptible to alteration. Our company shall not be liable > for the message if altered, changed or falsified. If you are not the > intended recipient of this message, please delete it and notify the sender. > Although all reasonable efforts have been made to keep this > transmission free from viruses, the sender will not be liable for > damages caused by a transmitted virus. > ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
