I've sent a PR to fix this issue: https://github.com/wso2/carbon-commons/pull/215/files
On Fri, Apr 8, 2016 at 1:44 PM, Nirmal Fernando <[email protected]> wrote: > This explains : > https://github.com/wso2/carbon-commons/blob/master/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider/InMemoryLogProvider.java#L237 > > On Fri, Apr 8, 2016 at 1:19 PM, Nirmal Fernando <[email protected]> wrote: > >> Did anyone check this issue with clearLogs ? It seems it's not working >> still. >> >> On Thu, Apr 2, 2015 at 5:08 PM, Maheeka Jayasuriya <[email protected]> >> wrote: >> >>> Hi Saneth/Waruna, >>> >>> I was able to resolve the issue by using the before log length and after >>> log length and iterating between these two counts. >>> >>> There still seem to be an issue with the clearLogs() even when tested >>> with a 100000 sec wait. Therefore, I am sticking with above approach. >>> >>> Thanks, >>> Maheeka >>> >>> >>> Maheeka Jayasuriya >>> Software Engineer >>> Mobile : +94777750661 >>> >>> On Wed, Apr 1, 2015 at 2:33 PM, Saneth Dharmakeerthi <[email protected]> >>> wrote: >>> >>>> Hi Maheeka, >>>> >>>> You can filter the logs while iterating over the logs using >>>> "logEvent.getLogTime()" which return the logged time in the format of >>>> "2015-04-01 14:16:07,187". You need to covert this to a timestamp and >>>> filter only logs that was created within the test method scope. >>>> >>>> >>>> Thanks and Best Regards, >>>> >>>> Saneth Dharmakeerthi >>>> Senior Software Engineer >>>> WSO2, Inc. >>>> Mobile: +94772325511 >>>> >>>> On Wed, Apr 1, 2015 at 1:05 PM, Waruna Perera <[email protected]> wrote: >>>> >>>>> Hi Maheeka, >>>>> >>>>> Avoid using sleep. Use time out function. >>>>> >>>>> Thanks, >>>>> >>>>> On Wed, Apr 1, 2015 at 12:35 PM, Maheeka Jayasuriya <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Waruna, >>>>>> >>>>>> In that case, what would be the alternative to do the above? Since >>>>>> iterating over the new logs (using before length and after length) also >>>>>> did >>>>>> not work for me. Or is the issue only in a delay? If so a sleep would >>>>>> solve >>>>>> the issue? >>>>>> >>>>>> Thanks, >>>>>> Maheeka >>>>>> >>>>>> Maheeka Jayasuriya >>>>>> Software Engineer >>>>>> Mobile : +94777750661 >>>>>> >>>>>> On Wed, Apr 1, 2015 at 11:20 AM, Waruna Perera <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi Maheeka, >>>>>>> >>>>>>> We have encountered issue with delay of clear logs in our test cases >>>>>>> at times. So you will have to consider that. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Waruna >>>>>>> >>>>>>> On Wed, Apr 1, 2015 at 11:15 AM, Maheeka Jayasuriya < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I want to read the logs in ESB to do perform a few assertions. >>>>>>>> However, since I have multiple test methods in the test case, I am >>>>>>>> unable >>>>>>>> to find the correct required log. >>>>>>>> >>>>>>>> To further elaborate, my first test case prints 20 of required logs >>>>>>>> and the second test case prints 100. When I iterate through all logs, >>>>>>>> although logViewer.clearLogs() is done at the start of each method, the >>>>>>>> count for the second run test case is 120 and not 20 or 100 (I am >>>>>>>> verifying >>>>>>>> the log count in the test case). I verified with the log length before >>>>>>>> and >>>>>>>> after clearLogs() is called and the length remains the same. What is >>>>>>>> the >>>>>>>> expectation of the clearLogs() method. Does it clear all the system >>>>>>>> logs or >>>>>>>> something else? >>>>>>>> >>>>>>>> If I use the length of the logs before and after the test >>>>>>>> functionality and iterate through that, the required logs are not >>>>>>>> available. >>>>>>>> >>>>>>>> Also believe, logViewer.getAllRemoteSystemLogs() is the successor >>>>>>>> to deprecated method logViewer.getAllSystemLogs() ? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Maheeka >>>>>>>> >>>>>>>> Maheeka Jayasuriya >>>>>>>> Software Engineer >>>>>>>> Mobile : +94777750661 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Waruna Perera >>>>>>> Senior Software Engineer - Test Automation >>>>>>> Mobile: +94 77 3867037 >>>>>>> WSO2, Inc.; http://wso2.com/ >>>>>>> lean . enterprise . middlewear. >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Waruna Perera >>>>> Senior Software Engineer - Test Automation >>>>> Mobile: +94 77 3867037 >>>>> WSO2, Inc.; http://wso2.com/ >>>>> lean . enterprise . middlewear. >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Team Lead - WSO2 Machine Learner >> Associate Technical Lead - Data Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> > > > -- > > Thanks & regards, > Nirmal > > Team Lead - WSO2 Machine Learner > Associate Technical Lead - Data Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > -- Thanks & regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
