geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan <xhh...@gmail.com>
Subject Re: Issue regarding GeronimoLog
Date Fri, 20 Aug 2010 01:33:54 GMT
Hi,
    Refer to this thread, it should be helpful.

http://apache-geronimo.328035.n3.nabble.com/Application-specific-log4j-issue-tc863758.html#a863758


2010/8/19 Anil Chawla <achawla@us.ibm.com>

> Hi,
> We are moving our application to Geronimo and are encountering an issue
> with GeronimoLog. The core problem is that we are using the Apache Pig
> library and need to serialize objects created by that library. The Pig
> classes use the commons logging framework and unfortunately maintain Log
> references as instance fields rather than static fields -- which means that
> the Log field is also serialized when the object is serialized. This causes
> a failure on Geronimo when trying to serialize the Pig objects because the
> GeronimoLog implementation is not serializable. We are trying to find a
> solution without modifying all of the Pig classes.
>
> The only solution we have found so far is to dynamically set the
> "org.apache.commons.logging.LogFactory" system property when our application
> starts in order to replace the GeronimoLogFactory implementation with our
> own custom LogFactory implementation. Our custom LogFactory wraps
> GeronimoLog in order to make it serializable without breaking the normal
> server logging behavior. The problem with this approach is that it changes
> the LogFactory implementation for the entire VM and our classes are not
> available to other applications in the container.
>
> * Is there a way to replace the LogFactory/Log implementation but isolate
> that change to a specific WAR/EAR within Geronimo?
>
> * Are there any other ideas on how we might work around this issue?
>
> Thanks so much!
>
> Anil Chawla
>



-- 
Ivan

Mime
View raw message