By default, too many traces logged for each SOAP request/reply.
Article ID: KB0092603
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
By default, too many traces are being written in the logs for SOAP request reply in BW 5.11.
The resemble the following:
65047 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - Internal Update inputMessage
65047 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - Fixing slot: inputMessage
65047 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - SLOT: EchoRequestElement(array=false any=false complex=true)
65047 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - Looking for complex type EchoRequestElement in inputMessage
65048 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - SLOT: mimeEnvelopeElement(array=false any=false complex=true)
65048 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - Looking for complex type mimeEnvelopeElement in inputMessage
65048 [JobCourier6] INFO com.tibco.spin.soap.processors.filters.ArrayTypeReductionSaxFilter - SLOT: headers(array=false any=false complex=true)
Issue/Introduction
Resolution
# ============================================================================
# 2. TIBCO BusinessWorks Logger. The logger "bw.logger" can be used by the
# third party application or java code executing in the TIBCO BusinessWorks
# JVM to write the log messages to the TIBCO BusinessWorks log file.
# TIBCO BusinessWorks Logger. The logger level is "INFO" and the appender
# is "tibco_bw_log".
log4j.logger.bw.logger=INFO, tibco_bw_log
- Change INFO to WARN. Make this change in the log4j.properties file.
- Restart Designer.
Feedback
