The problem occurs because the Orbeon webapp sets a system property
named "log4j.configuration" in the org.orbeon.oxf.util.LoggerFactory.
Because this value is deliberately set to a bogus value, any webapps
in the same JVM (same tomcat in this case) that start after Orbeon,
will fail using the regular configuration discovery mechanisms of Log4j.
I am not sure if the conditions for this design decision are still
present. They might be. My opinion is that any webapp that sets a
system property better have an extremely good reason for doing so,
given that system properties are shared across the entire JVM, not
just webapp.
Our solution was to programmatically configure Log4j by loading the
properties manually and then call the PropertiesConfigurator in
Log4j. Another option would be to modify the source in Orbeon, or to
petition the Orbeon development team to fix this issue.
On Apr 30, 2008, at 8:02 AM, .::: Markku :::. wrote:
>> The log works fine when we develop in Eclipse with multiple webapp.
>> But when we install on a server, it don't work any more. If we
>> remove orbeon, all the others webapp log correctly. We use orbeon
>> 3.5. In Eclipse, if we choice to "publish module contexts to
>> separate XML files", there is only log of orbeon like on the
>> server. Here is the problem : if there is separate context file,
>> only orbeon can write log.
>
> Same for me, in Eclipse (SDK 3.2.0 with WTP 1.5.0) the logging of
> all web applications works fine but when the same web applications
> are deployed to a server (Apache Tomcat 5.5.23) the logging of my
> own web applications fails/stops. I am using Orbeon Forms
> (3.6.0.200712181809) as separate deployment.
>
> I tried to deactivate different appenders in Orbeon Forms's
> log4j.xml file in order to test if they are conflicting with my own
> web applications' appenders--didn't help.
>
> The logging of my own web applications started to work not until I
> removed Orbeon Forms from the server. Couldn't find any hints by
> browsing through Tomcat logs :(
>
> If somebody figures out what causes the problem, please let me and
> others know.
>
> Thanks in advance!
>
>
> -Markku
>
> --
> You receive this message as a subscriber of the
ops-users@...
> mailing list.
> To unsubscribe: mailto:
ops-users-unsubscribe@...
> For general help: mailto:
sympa@...?subject=help
> OW2 mailing lists service home page:
http://www.ow2.org/wws--
You receive this message as a subscriber of the
ops-users@... mailing list.
To unsubscribe: mailto:
ops-users-unsubscribe@...
For general help: mailto:
sympa@...?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws