Created [1] to track this, and did some initial changes.
[1]. https://issues.apache.org/jira/browse/STRATOS-962
On Mon, Nov 10, 2014 at 10:53 AM, Isuru Perera wrote:
> +1. We need change such redundant log messages to "DEBUG" level and keep
> only the required logs in "INFO" level.
>
> On Sun,
+1. We need change such redundant log messages to "DEBUG" level and keep
only the required logs in "INFO" level.
On Sun, Nov 9, 2014 at 11:33 PM, Isuru Haththotuwa
wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Top
+1
However when reducing log entries IMO it should be taken in to
consideration if the particular log entries are actually redundant or if
they are representing unique code paths, which can help in initial
"debugging" itself.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog
+1
On Sunday, November 9, 2014, Isuru Haththotuwa wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has already been
> upd
+1 Isuru.
Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 10, 2014 1:24 AM, "Nirmal Fernando" wrote:
> +1 from me too.
>
> On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa
> wrote:
>
>> Hi Devs,
>>
>> I think we need to $subject, specially in the messaging component. In
+1 from me too.
On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has al
+1 for doing this..This will help debugging issues specially with composite
application, since multiple clusters associated with an application, the
flow cannot be predicted using the logs since logs include publisher as
well as subscriber for the single JVM.
On Sun, Nov 9, 2014 at 11:33 PM, Isuru
Hi Devs,
I think we need to $subject, specially in the messaging component. In
single JVM, since we have only one Topology model, and three sets of
updaters, there are multiple logs indicating that Topology has already been
updated.
For an example when a service created, there will be multiple le
