airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lahiru Gunathilake <glah...@gmail.com>
Subject Re: Issues with slf4j with axis2
Date Sun, 21 Oct 2012 04:59:19 GMT
I just tested the logging and it works fine ... Thanks patanachai for the
quick fix !


Lahiru

On Sun, Oct 21, 2012 at 12:18 AM, Lahiru Gunathilake <glahiru@gmail.com>wrote:

>
>
> On Sat, Oct 20, 2012 at 9:22 PM, Suresh Marru <smarru@apache.org> wrote:
>
>> Thank very much Patanachai for prompt response and all the clean up. I
>> ran the slf4j-migrator and as far as I can tell all of Airavata  code base
>> is now only using slf4j logging.
>>
>> I plan to branch and call a release vote tomorrow morning.
>>
> Before a release vote we need to do an RC and test it I guess.
>
>
> Lahiru
>
>>
>> Lahiru, Can you please verify tomcat logging and make any necessary
>> changes?
>>
>> Hi All,
>>
>> Last call before code freeze, any changes to be made before the 0.5
>> release?
>>
>> Cheers,
>> Suresh
>>
>>
>> On Oct 20, 2012, at 10:33 AM, Lahiru Gunathilake <glahiru@gmail.com>
>> wrote:
>>
>> > Hi Patanachai,
>> >
>> > Theoratically it should work, but I moved one service in to
>> commons-logging
>> > with same configuration it works fine. The issue was File appender, I
>> > cannot get the logs in to a file. Axis2 to also uses commons-logging as
>> > logging implementation.
>> >
>> > Patanachai, if you think this is unnecessary can you please revert my
>> > commit and fix it ..
>> >
>> > Lahiru
>> >
>> >
>> > On Sat, Oct 20, 2012 at 10:10 AM, Suresh Marru <smarru@apache.org>
>> wrote:
>> >
>> >> Right on Patanachai!!
>> >>
>> >> Lahiru,
>> >>
>> >> What Patanachai makes sense, the fact that all logs are going to
>> >> catalina.out indicates they are streaming to stdout. May be we should
>> >> remove all slf4j-simple with slf4j-log4j12. If that does not still
>> address
>> >> the problem then we should look into log4j-over-slf4j for axis2 to
>> bridge
>> >> it.
>> >>
>> >> Suresh
>> >>
>> >> On Oct 19, 2012, at 11:29 PM, ptangcha@umail.iu.edu wrote:
>> >>
>> >>> Hi Devs,
>> >>>
>> >>> I agree with Suresh.
>> >>> SLF4J is just a log facade library. It is suitable for integrating
>> with
>> >> any
>> >>> logging library and this provides more flexibility to users. It should
>> >> work
>> >>> well even with log4j if you deploy it with slf4j-log4j.jar. Moreover,
>> >> log4j
>> >>> and slf4j-log4j can be co-deployed on the same environment.
>> >>>
>> >>> "put them in to a separate file rather putting in to catalina.out
>> when we
>> >>> deploy on tomcat"
>> >>> IMHO, this seems to be a configuration more than implementation
>> problem.
>> >>> This might imply that we use slf4j-simple.jar and every log message
is
>> >>> redirected to standard out by this library. (or not deploy any logging
>> >>> library which slf4j-api [version < 1.6] will automatically use
>> >> slf4j-simple)
>> >>>
>> >>> I don't know what problem Lahiru faced with slf4j and axis2. But, I
>> >> prefer
>> >>> to stick with slf4j in airavata implementation.
>> >>>
>> >>> Patanachai
>> >>>
>> >>> On Fri, Oct 19, 2012 at 11:59 AM, Suresh Marru <smarru@apache.org>
>> >> wrote:
>> >>>
>> >>>> Hi Lahiru,
>> >>>>
>> >>>> It is important that we have one logging across all of Airavata
>> >> modules. I
>> >>>> agree axis2 compatibility is an important one, but we should also
be
>> >>>> forward looking.
>> >>>>
>> >>>> Looks like you are contradicting yourself - [1] :)
>> >>>>
>> >>>> I see log4j is superseded by logback [2]? any insights on if we
will
>> run
>> >>>> into class loading issues or other complaints on log4J?
>> >>>>
>> >>>> Here is a trace of previous changes [3].
>> >>>>
>> >>>>
>> >>>> Suresh
>> >>>>
>> >>>> [1] - http://markmail.org/message/lzosuifvlusyzhzy
>> >>>> [2] - http://logback.qos.ch/reasonsToSwitch.html
>> >>>> [3] - https://issues.apache.org/jira/browse/AIRAVATA-107
>> >>>>
>> >>>> On Oct 19, 2012, at 2:31 PM, Lahiru Gunathilake <glahiru@gmail.com>
>> >> wrote:
>> >>>>
>> >>>>> Hi Devs,
>> >>>>>
>> >>>>> I have seen some issues with slf4j when using with axis2 logging,
>> and I
>> >>>>> have seen some people complaining about this. I think its very
>> >> important
>> >>>>> that we have proper logging and put them in to a separate file
>> rather
>> >>>>> putting in to catalina.out when we deploy on tomcat.
>> >>>>>
>> >>>>> I think it would be great if we can have separate logs per services
>> (we
>> >>>>> have mainly 4 services) and things will be very nice forthe
>> >>>> administrator.
>> >>>>> If we want to do this we should go ahead with axis2 friendly
logging
>> >>>>> implementation.
>> >>>>>
>> >>>>> I just tested with log4j and things works fine, if there are
no
>> >>>> objections
>> >>>>> I dn't mind moving airavata logging to log4j.
>> >>>>>
>> >>>>> Lahiru
>> >>>>>
>> >>>>> --
>> >>>>> System Analyst Programmer
>> >>>>> PTI Lab
>> >>>>> Indiana University
>> >>>>
>> >>>>
>> >>
>> >>
>> >
>> >
>> > --
>> > System Analyst Programmer
>> > PTI Lab
>> > Indiana University
>>
>>
>
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University
>
>


-- 
System Analyst Programmer
PTI Lab
Indiana University

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message