Sure Niranda, Let me know whether I have to report this in CEP or DAS?

On Sat, Apr 2, 2016 at 12:21 PM, Niranda Perera <nira...@wso2.com> wrote:

> Hi Udara,
>
> Ah. Never came across it but yes, you are correct. This seems to be a UI
> bug.
>
> Can you report a JIRA in this?
>
> Rgds
> On Apr 2, 2016 21:45, "Udara Rathnayake" <uda...@wso2.com> wrote:
>
>> Hi Niranda,
>>
>> ​If we edit and save an existing stream definition (without going to the
>> persistence UI)​ this can happen right? I have faced similar thing but
>> never tried reproducing.
>>
>> However we should bring tooling support(dev studio) ASAP to DAS
>> artifacts, so we can create and deploy via car apps easily.
>>
>>
>> On Fri, Apr 1, 2016 at 11:32 AM, Niranda Perera <nira...@wso2.com> wrote:
>>
>>> Hi Chehara,
>>>
>>> It's highly unlikely that a stream persistence configuration to get
>>> disabled automatically. Looks like someone have mistakenly disabled it from
>>> the UI. As per the current persistence UI, there is a possibility that such
>>> an incident may occur.
>>>
>>>
>>> On Fri, Apr 1, 2016 at 8:43 PM, Chehara Pathmabandu <cheh...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Solved. event persistent had been disabled automatically.
>>>>
>>>> On Fri, Apr 1, 2016 at 8:16 PM, Niranda Perera <nira...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Yasara,
>>>>>
>>>>> We need to find where exactly the data stopped persisting. can you
>>>>> find the final entry? Are there any error in the logs?
>>>>>
>>>>> also, we need to check the mysql connections. Check if it has grown
>>>>> out of proportion as previously.
>>>>> And the CPU and memory usage of the node.
>>>>>
>>>>> On Fri, Apr 1, 2016 at 7:37 PM, Mohanadarshan Vivekanandalingam <
>>>>> mo...@wso2.com> wrote:
>>>>>
>>>>>> [Adding Dev mail thread]
>>>>>>
>>>>>> @Niranda, can you please dig on this issue and find the root cause..
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 1, 2016 at 7:26 PM, Yasara Dissanayake <yas...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> As you can see from the image attached here[1]:
>>>>>>> Current status is growing as the data receive and we use this same
>>>>>>> stream to persist. But from a particular date data had not been 
>>>>>>> persisted.
>>>>>>>
>>>>>>> regards,
>>>>>>> yasara
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *V. Mohanadarshan*
>>>>>> *Senior Software Engineer,*
>>>>>> *Data Technologies Team,*
>>>>>> *WSO2, Inc. http://wso2.com <http://wso2.com> *
>>>>>> *lean.enterprise.middleware.*
>>>>>>
>>>>>> email: mo...@wso2.com
>>>>>> phone:(+94) 771117673
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Niranda Perera*
>>>>> Software Engineer, WSO2 Inc.
>>>>> Mobile: +94-71-554-8430
>>>>> Twitter: @n1r44 <https://twitter.com/N1R44>
>>>>> https://pythagoreanscript.wordpress.com/
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Chehara Pathmabandu
>>>> *Software Engineer - Intern*
>>>> Mobile : +94711976407
>>>> cheh...@wso2.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Niranda Perera*
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-71-554-8430
>>> Twitter: @n1r44 <https://twitter.com/N1R44>
>>> https://pythagoreanscript.wordpress.com/
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> UdaraR
>>
>


-- 
Regards,
UdaraR
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to