What we did in our installation was to edit the esb/conf/log4j.xml
where you add an appender for each classpath you want to log (e.g.
com.somecompany.mypackage) which points to a log file: I would use
RollingFileAppender so the files don't get too big. Then add a logger
element for the package and use the appender that you've defined.
Lance Finn Helsten
[email protected]
On 4 May 2009, at 18:49, Corrado Campisano wrote:
Hi,
I got problems with log4j too, when trying to do the same.
Maybe I'm not so proficient with log4j, but...
Is there any generic sample we can replicate?
Best regards.
Corrado
2009/5/4 bobob <[email protected]>
Hi
In my ServiceMix application platform, I will be having multiple SA
running
for different services. But I don't want to have only one log file
for
standalone servicemix ESB, that is harder for debugging each service
running. but I don't know how to cofigure log4j.xml on root and SA
level
in
order to have each SA service come up with each own log file.
I did a search on this forrum and it seems to me that this topic was
discussed before. However, I can not find out that thread. If you
happened
to know, can you paste a link here or will be appreciated if you
shed me a
light.
Thanks!
--
View this message in context:
http://www.nabble.com/How-to-configure-log4j-for-generating-log-file-for-each-SA--tp23377239p23377239.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
