commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: [logging] Logging problems with log4j - [SOLVED]
Date Tue, 22 Jun 2004 21:18:34 GMT
great :)

i've added a FAQ about this  
(http://wiki.apache.org/jakarta-commons/Logging/ 
FrequentlyAskedQuestions) but i've never used WebSphere so it's  
possible i've made some mistakes. i'd be grateful if people could spend  
a couple of minutes checking it over and added whatever improvements  
they can.

TIA

- robert

On 22 Jun 2004, at 19:17, Pingili, Madhupal wrote:

> Hello All,
> Thanks to all who have responded to this post.
> Here are the settings that solved the problem:
> After deploying J2EE app (.ear) on WAS 5.1, make sure you have
> Classloader mode as PARENT_LAST  and WAR Classloader Policy as
> Application.
>
> Now it's logging all messages it is supposed to log, just like the app
> on WAS 4.0.4.
>
>
> Reddy Pingili
>
>> -----Original Message-----
>> From:	David J. M. Karlsen [SMTP:david@davidkarlsen.com]
>> Sent:	Tuesday, June 22, 2004 6:30 AM
>> To:	robertburrelldonkin@blueyonder.co.uk
>> Cc:	Jakarta Commons Users List
>> Subject:	Re: [logging] Logging problems with log4j
>>
>> robert burrell donkin wrote:
>>
>> That's because websphere5.1 uses commons-logging itself - try setting
>> your EAR to use PARENT_LAST classloading - so that the classes you
>> provide (and commons-logging.properties) are found first.
>>
>> Kind regards,
>>
>> David Karlsen
>>
>>> hi
>>>
>>> i don't know of any particular problems with websphere 5.1 (does  
>>> anyone
>>
>>> else?) but classpath issues are common in containers. you might have
>>> more luck using an alternative configuration mechanism such as the  
>>> jdk
>>> 1.3 jar service discovery mechanism.
>>>
>>> if you really want to use this commons-logging.properties file
>>> mechanism then it's possible that if websphere has a version of
>>> commons-logging in it's root classloader then you'll need to put it  
>>> in
>>> the root. of course, if this is the case, you'll also need to drop in
>>> the newer jar over the older.
>>>
>>> - robert
>>>
>>> On 21 Jun 2004, at 21:17, Pingili, Madhupal wrote:
>>>
>>>> Hello All,
>>>> I am new to this user list. I am using commons logging latest
>>>> version which uses log4j in a web application:
>>>>
>>>> commons-logging.properties:
>>>>
>>>> org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4J 
>>>> Log
>>
>>>> ger
>>>>
>>>> I have log4j.properties in the web app classpath i.e.
>>>> /WEB-INF/classes/log4j.properties.
>>>>
>>>> When I deploy this web app on WebSphere 5.1, it looks like log4j is  
>>>> not
>>>> initializing at all.
>>>> It is not creating any log files for any log messages to be written.
>>>>
>>>> Are there any known problems with commons-logging on WebSphere 5.1?
>>>>
>>>> Any help is appreciated.
>>>>
>>>>
>>>> Reddy Pingili
>>>>
>>>>
>>>> -------------------------------------------------------------------- 
>>>> -
>>>> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:  
>>>> commons-user-help@jakarta.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>>
>>
>>
>> -- 
>> David J. M. Karlsen - +47 90 68 22 43
>> http://www.davidkarlsen.com
>> http://mp3.davidkarlsen.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Mime
View raw message