10 messages in org.apache.logging.log4j-userRe: multiple web-apps in separate log...| From | Sent On | Attachments |
|---|---|---|
| James Stauffer | Jan 21, 2005 11:31 am | |
| Ceki Gülcü | Jan 21, 2005 11:49 am | |
| Jacob Kjome | Jan 21, 2005 12:39 pm | |
| James Stauffer | Jan 21, 2005 3:10 pm | |
| Jacob Kjome | Jan 21, 2005 4:58 pm | |
| James Stauffer | Jan 21, 2005 5:06 pm | |
| Jacob Kjome | Jan 22, 2005 8:02 am | |
| Ceki Gülcü | Jan 22, 2005 9:49 am | |
| Jacob Kjome | Jan 22, 2005 10:45 am | |
| Ceki Gülcü | Jan 22, 2005 11:13 am |
| Subject: | Re: multiple web-apps in separate logging contexts | |
|---|---|---|
| From: | Ceki Gülcü (ce...@qos.ch) | |
| Date: | Jan 22, 2005 9:49:35 am | |
| List: | org.apache.logging.log4j-user | |
At 05:02 PM 1/22/2005, you wrote:
At 07:06 PM 1/21/2005 -0600, you wrote:
So for 1.2 I need to use a custom repository selector from the sandbox and in 1.3 there is one available in the core. Is that correct?
Yup!
But there are other differences. In 1.3, the "log4j.repositorySelector" system property is processed by LogManager, in 1.2.x that system property has no effect. Moreover, in 1.3, ContextJNDISelector will also configure your named repository when it creates it. In 1.2, it will just create it leaving to you the responsibility of configuring it.
In 1.3, you can detach a repository by name. In 1.2.x you cannot. So, when your web-app is recycled you can shutdown and detach it whereas in 1.2 your repository will not be recycled along with your web-app. See also [1] o.a.l.selector.servlet.ContextDetachingSCL.
These are small differences but which sometimes can add up to make a big difference.
Oh, and I forgot to mention the internal logs generated by log4j itself.
Jake
-- Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/