On Mon, May 7, 2012 at 9:47 AM, Amani Soysa <[email protected]> wrote: > Yes you cannot view the stacktrace from the current logging > implementation, because we are using file systems to store logs and we are > filtering logs line by line
Amani, You should rather use a regex to identify the exception block. You cannot pass a log file with exception line by line and produce an intelligent output. eg. See http://stackoverflow.com/questions/3814327/regular-expression-to-parse-a-log-file-and-find-stacktraces http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/log4j/varia/LogFilePatternReceiver.html(from Chainsaw) > . This can be fixed by using a custom appender like CassandraAppender or > DBAppender. > > However most of the ESB related logs cannot be extracted using the current > logging implementation because synapse component is not multi-tenant. There > is another issue[1] related to this we are in the process of fixing this > issue. > > [1] - https://wso2.org/jira/browse/STRATOS-549 > > Regards > Amani > > > On Mon, May 7, 2012 at 9:34 AM, Afkham Azeez <[email protected]> wrote: > >> Actually there are major issues with logging. When most things fail, you >> cannot see any logs as a tenant. We genrally request for the logs from >> Sanjaya. So to make this useful, the log UI should show detailed >> stacktraces. >> >> >> On Mon, May 7, 2012 at 7:32 AM, Amani Soysa <[email protected]> wrote: >> >>> >>> >>> On Sat, May 5, 2012 at 1:43 PM, Afkham Azeez <[email protected]> wrote: >>> >>>> I just tried the sample in this article and everything works perfectly. >>>> >>>> However, there is a major usability issue. Non of the messages logged >>>> by the log mediator are visible in the Stratos logs section. Nor are the >>>> error logs visible. Amani, can you look into this and fix it ASAP? >>>> >>> Yes I will look into this. >>> >>>> >>>> >>>> On Sat, May 5, 2012 at 1:13 PM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> See the comment from a user on >>>>> http://wso2.org/library/articles/2011/01/wso2-esb-by-example-service-chaining >>>>> >>>>> Perhaps this is fixed now. >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- /sumedha +94 773017743
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
