Please stop spamming this list by sending the same post repeatedly. There
are plenty of articles on the Web discussing SOAP message logging in Axis2.
Did you actually do your own research?

On Wed, Jan 27, 2010 at 12:01, <arockia.s...@aciworldwide.com> wrote:

>
> Thanks & Regards,
> Arockia
>
> This email message and any attachments may contain confidential,
> proprietary or non-public information.  The information is intended solely
> for the designated recipient(s).  If an addressing or transmission error has
> misdirected this email, please notify the sender immediately and destroy
> this email.  Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited.  Any opinions expressed
> in this email are those of the author personally.
>
>
>  From: arockia.s...@aciworldwide.com To:
> axis-dev@ws.apache.org
> Date: 01/26/2010 11:10 PM
>  Subject: Re: Axis213  Soap request and response logging issue
>
> ------------------------------
>
>
>
>
> Thanks & Regards,
> Arockia
>
> This email message and any attachments may contain confidential,
> proprietary or non-public information.  The information is intended solely
> for the designated recipient(s).  If an addressing or transmission error has
> misdirected this email, please notify the sender immediately and destroy
> this email.  Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited.  Any opinions expressed
> in this email are those of the author personally.
>
>   From: arockia.s...@aciworldwide.com  To: axis-dev@ws.apache.org  Date: 
> 01/26/2010
> 10:57 PM  Subject: Re: Axis213  Soap request and response logging issue
>
>  ------------------------------
>
>
>
>
> Thanks & Regards,
> Arockia
>
> This email message and any attachments may contain confidential,
> proprietary or non-public information.  The information is intended solely
> for the designated recipient(s).  If an addressing or transmission error has
> misdirected this email, please notify the sender immediately and destroy
> this email.  Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited.  Any opinions expressed
> in this email are those of the author personally.
>   From: arockia.s...@aciworldwide.com  To: axis-dev@ws.apache.org  Date: 
> 01/26/2010
> 07:36 PM  Subject: Axis213  Soap request and response logging issue
>
>
>  ------------------------------
>
>
>
>
> Hi All,
>
> In axis213 for Soap REQUEST AND RESPONSE LOGGING I put the below entry in
> the configuration file called balilogger.lcf.
>
> # To log SOAP Messages enable this
> log4j.logger.org.apache.axis2.transport.http=DEBUG, LOGFILE
>
> # LOGFILE is set to be a File appender using a PatternLayout.
> log4j.appender.LOGFILE=bali.utils.BaliRollingFileAppender
> log4j.appender.LOGFILE.File=..//logs//${currentDate}//axismessages.log
> log4j.appender.LOGFILE.MaxFileSize=200MB
> log4j.appender.LOGFILE.MaxBackupIndex=100
> log4j.appender.LOGFILE.LogRetentionDays=7
> log4j.appender.LOGFILE.Append=true
> log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
> log4j.appender.LOGFILE.layout.ConversionPattern=%d{DATE};[%t];%p;%m%n
>
>
> It is not logging soap envelop and soap body. It logs some other related
> information in axismessages.log file
>
>
> But in Axis1 architecture it works fine.It is logging soap envelop and soap
> body also with other related information .
> I just put log4j.logger.org.apache.axis.transport.http=DEBUG, LOGFILE
>
> so please help me to find out the issue.
>
>
>
> Thanks & Regards,
> Arockia
>
> This email message and any attachments may contain confidential,
> proprietary or non-public information.  The information is intended solely
> for the designated recipient(s).  If an addressing or transmission error has
> misdirected this email, please notify the sender immediately and destroy
> this email.  Any review, dissemination, use or reliance upon this
> information by unintended recipients is prohibited.  Any opinions expressed
> in this email are those of the author personally.
>
>
>
>

Reply via email to