Sounds like a classloader configuration issue.  OC4J probably has a
version of log4j on their classpath and it's bleeding over into the
classpath of your webapps.  Is there a webapp-classpath-first setting
somewhere?

On Mon, Aug 9, 2010 at 10:06 AM, Jasmin Mehta <[email protected]> wrote:
> What you are suggesting may be true for JBoss. But I have it practically
> not working on OC4J.
>
> http://download-uk.oracle.com/docs/cd/B31017_01/web.1013/b28952/opensrc.htm#i637153
>
> According to this article, log4j.xml or log4j.properties plays the same
> role. I do have separate log4j.properties configured for each web
> application, pointing to different log directory and file name. But still
> it picks up the one which deploys first. Looks like limitation of OC4J.
>
> So that is why I am looking for option without using log4j at all.
>
>
>
> From:   Brent Worden <[email protected]>
> To:     [email protected]
> Date:   08/09/2010 09:56 AM
> Subject:        Re: [Logging] : Can commons.logging be used without log4j
>
>
> On 8/9/2010 7:53 AM, Jasmin Mehta wrote:
>> The log4j has limitation that if its used as a shared library then it
> can
>> initiate only one configuration. So my all we applications which shares
>> the same instance are populating the logs into only one log file (the
> web
>> app which deployed first in order), rather than individual / separate
> log
>> files configured in the path of each of the application's
>> log4j.properties.
>>
>>
> This isn't true.  Log4j allows for defining and using multiple log
> configurations in a single JVM.  This is accomplished by using a
> RepositorySelector to manage the multiple log hierarchies.  See
> http://community.jboss.org/wiki/Log4jrepositoryselector for a web
> container example.
>
> Thanks,
>
> Brent Worden
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
> ******************************************************************************
> This email and any files transmitted with it are intended solely for
> the use of the individual or agency to whom they are addressed.
> If you have received this email in error please notify the Navy
> Exchange Service Command e-mail administrator. This footnote
> also confirms that this email message has been scanned for the
> presence of computer viruses.
>
> Thank You!
> ******************************************************************************
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to