[ 
https://issues.apache.org/jira/browse/SYNAPSE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Asankha C. Perera resolved SYNAPSE-123.
---------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.0)
                   1.1
         Assignee: Asankha C. Perera

This can now be achieved via log4j.properties

Currently all services log to the SERVICE_APPENDER (see below)

# Configure the service logger at INFO level. Writes only 
run-time/mediation-time audit messages
log4j.category.SERVICE_LOGGER=INFO, SERVICE_APPENDER
log4j.additivity.SERVICE_LOGGER=false
log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
log4j.appender.SERVICE_APPENDER.File=logs/service.log
log4j.appender.SERVICE_APPENDER.MaxFileSize=1000KB
log4j.appender.SERVICE_APPENDER.MaxBackupIndex=10
log4j.appender.SERVICE_APPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.SERVICE_APPENDER.layout.ConversionPattern=%d{ISO8601} 
[%X{ip}-%X{host}] [%t] %5p %c{1} %m%n

However, if you want to have a logs/proxy1.log for your proxy service named 
"proxy1", create a new appender (say PROXY1_APPENDER with the location of the 
log file etc) and assign it to the category as below

log4j.category.SERVICE_LOGGER.proxy1=INFO, PROXY1_APPENDER


> Enhance log mediator to support unique log file per proxy/service
> -----------------------------------------------------------------
>
>                 Key: SYNAPSE-123
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-123
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.0
>         Environment: WinXP
>            Reporter: John Bouck
>            Assignee: Asankha C. Perera
>            Priority: Minor
>             Fix For: 1.1
>
>
> The log mediator puts all logs into one file.  Enhance the log mediator to 
> support unique log per proxy/service so that each service may/may not have 
> its own log file/location.  This will ease the deployment of Synapse in a 
> Gateway model of service proxy as logs need to be often constrained per 
> security restrictions (ie the service publisher may need to review the 
> synapse logs for their service, but should not have access to the logs of all 
> of the other proxy/services).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to