org.apache.cxf.common.logging.Slf4jLogger

If you want the complete request timed, you should simply use your access_log of the server you are using, which most certainly can log millis/seconds pr. request.

Another way, that I’ve been using, it a combination of a servlet filter and the perf4j library. In the servlet filter, I extracted the SOAP method name from the request and then logged through perf4j with SOAP method name as tag. That, in combination with perf4j’s grouped timing statistics gives a great, realtime picture of ws request traffic on each ws method.

07:25:03,845 – INFO Inbound Message
—————————-
ID: 1
Address:
Encoding:
Content-Type:
Headers:
Payload: <soap:Envelope………..
<soap continued…
<soap continued…
<soap continued…

07:25:04,920 – DEBUG Invoking HTTP method POST
07:25:04,920 – DEBUG URIMappingInterceptor can only handle HTTP GET, not HTTP POST

07:25:05,021 – DEBUG Entering my app for acct: 1234
…
…
…
07:25:10,004 – DEBUG Exiting my app for acct: 1234 – Elapsed time: 4986 ms.

07:25:10,010 – DEBUG Interceptors contributed by bus: [org.apache.cxf.interceptor.LoggingOutInterceptor@5522a7b5]
07:25:10,011 – DEBUG Interceptors contributed by service: []
07:25:10,011 – DEBUG Interceptors contributed by endpoint: [org.apache.cxf.interceptor.MessageSenderInterceptor@563087bd, org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@c1fb580, org.apache.cxf.jaxws.handler.logical.LogicalHandlerOutInterceptor@75c4ecb7, org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@53911ec8, org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@5c7c0754, org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor@52c54b3b]
07:25:10,011 – DEBUG Interceptors contributed by binding: [org.apache.cxf.interceptor.AttachmentOutInterceptor@16ce38f1, org.apache.cxf.interceptor.StaxOutInterceptor@3cfc61e9, org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@5d802746, org.apache.cxf.interceptor.WrappedOutInterceptor@892949f, org.apache.cxf.interceptor.BareOutInterceptor@4f5b571e, org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@75b49b45, org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor@243e0b62]
07:25:10,695 – INFO Outbound Message

As you can see above, actual time taken from A-Z (CXF entry to CXF exit) is:
07:25:03,845 —- to —- 07:25:10,695

However, i was able to capture only the time between:
07:25:05,021 —- to —- 07:25:10,004

This is misleading ‘cus I am only able to capture times within my app and not able to extend it to CXF.

Is there any way I can customize these interceptors to log the info the way I want?

Suggestions for clarifications are welcome though

Sorry for the late reply. For some reason I had not seen (or maybe forgotten about) your comment, so I first got around to moderating it now.

The file “org.apache.cxf.Logger” should ONLY contain the one line “org.apache.cxf.common.logging.Log4jLogger” to enable log4j logging. Actually configuring log4j log levels etc., you need to look to the log4j project to learn about.

Log4j both have a .properties config file format and a xml config file format you can use. I’ve always used the xml config file. You can also configure it programmatically.

If you place a file “log4j.xml” in the root of your classpath, log4j will automatically find and load that one.

You can also place it outside classpath, and provide the system property “-Dlog4j.configuration=file://….path to your file”.

If for some some reason you have trouble making log4j find and load your config, try setting “-Dlog4j.debug=true” on cmdline, at it will tell a whole lot about its bootstrapping/config loading.

See also: http://logging.apache.org/log4j/1.2/manual.html

1. in your source code make a META-INF/cxf directory

2. create a file in that directory, specificly named “org.apache.cxf.Logger”

3. Write one single line in that file, with the content “org.apache.cxf.common.logging.Log4jLogger”

Make sure that your build process, being it ant, maven or something else, includes the META-INF/cxf catalogue in your compiled output (e.g., ensure it is included in your runtime classpath when your app executes somewhere).

Your clarification in the comments
“Create the META-INF/cxf/org.apache.cxf.Logger file somewhere on your classpath. If you are building a war, for instance, it should end up in WEB-INF/classes/META-INF/cxf/org.apache.cxf.Logger (or inside a jar in WEB-INF/lib).”

Was just what I needed to get log4j and cxf playing together

Regards,
Frank

It looks like, that you have turned on log4j debugging of all of cxf. For outbound and inbound logging, you need only turn debugging on for these two logger names:

org.apache.cxf.interceptor.LoggingInInterceptor

org.apache.cxf.interceptor.LoggingOutIntercepto

Let me eloborate my Question,

Now my logger is logging all the activities like
———————————————————
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.jaxws.interceptors.HolderOutInterceptor@52a852a8
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] interceptors.HolderOutInterceptor – op: [OperationInfo: {http://services.vzw.com/}getReferenceData]
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] interceptors.HolderOutInterceptor – op.hasOutput(): true
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] interceptors.HolderOutInterceptor – op.getOutput().size(): 1
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.jaxws.interceptors.SwAOutInterceptor@51fa51fa
2010-06-22 10:30:23,243 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor@52885288
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.binding.soap.interceptor.SoapHeaderOutFilterInterceptor@4d9c4d9c
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.binding.soap.interceptor.SoapPreProtocolOutInterceptor@4ef84ef8
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.interceptor.MessageSenderInterceptor@4fee4fee
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Adding interceptor org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor@50065006 to phase prepare-send-ending
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Chain org.apache.cxf.phase.PhaseInterceptorChain@67b667b6 was modified. Current flow:
pre-logical [HolderOutInterceptor, SwAOutInterceptor, WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
post-logical [SoapPreProtocolOutInterceptor]
prepare-send [MessageSenderInterceptor]
pre-stream [LoggingOutInterceptor, AttachmentOutInterceptor, StaxOutInterceptor]
write [SoapOutInterceptor]
marshal [WrappedOutInterceptor, BareOutInterceptor]
prepare-send-ending [MessageSenderEndingInterceptor]

2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.interceptor.LoggingOutInterceptor@67ac67ac
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.interceptor.AttachmentOutInterceptor@4d424d42
2010-06-22 10:30:23,258 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Invoking handleMessage on interceptor org.apache.cxf.interceptor.StaxOutInterceptor@4d784d78
2010-06-22 10:30:23,274 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Adding interceptor org.apache.cxf.interceptor.StaxOutInterceptor$StaxOutEndingInterceptor@47cc47cc to phase pre-stream-ending
2010-06-22 10:30:23,274 DEBUG [WebContainer : 0] phase.PhaseInterceptorChain – Chain org.apache.cxf.phase.PhaseInterceptorChain@67b667b6 was modified. Current flow:
pre-logical [HolderOutInterceptor, SwAOutInterceptor, WrapperClassOutInterceptor, SoapHeaderOutFilterInterceptor]
post-logical [SoapPreProtocolOutInterceptor]
prepare-send [MessageSenderInterceptor]
pre-stream [LoggingOutInterceptor, AttachmentOutInterceptor, StaxOutInterceptor]
write [SoapOutInterceptor]
marshal [WrappedOutInterceptor, BareOutInterceptor]
——————————————————-

Where as what we actually need is the inbound and outbound soap msg/fault….
is it possible by any means to stop this and log only required part.

Thanks
Dharm

–Thanks
Dharm

The post as such is not about configuring log4j, but about if you already have log4j configured for your own system, how to make CXF log through that same configuration instead of JDK logger.

So, if your problems are related to log4j configuration itself, this post will not help you that much.

One tip though: A good place to start with log4j config debugging is starting your app with “-Dlog4j.debug=true”, as this will make it output how it initializes itself at bootstrap.

Thanks for the useful info. i tried the steps above but still cannot see the logging work. no one mentioned where to create the log4j property or xml file to specify the log file name and location. can some one advise pl….

regards
Paul Henderson

Details are available on http://cxf.apache.org/docs/debugging-and-logging.html , paragraph “Using SLF4J Instead of java.util.logging (since 2.2.8)”.

Hope this helps,

Cyrille

That is strange. Don’t know what happen there. The inbound and outbound messages are logged on two separately named loggers, so they should come as separate lines too.

The extra log is due to I have configured Logging Interceptors in log4j.properties. Thanks for your continuous help. Finally it works fine. Thanks polesen.

Final clarification:
Now the logged Inbound and Outbound messages are printed in single line. Is there possible to log the messages as seperate lines.

“logs twice”.

Hmm. Strange. Could you provide a small sample of a couple of log statements as they appear when you see them twice?